bpf-next is OPEN

And we're back open. ;-) Thanks, Daniel

bpf-next is OPEN

bpf-next is OPEN

v5.4-rc1 tag is just out and merge window over, therefore bpf-next back in business. Thanks, Daniel

bpf-next is OPEN

Merge window is closed, therefore new round begins. Thanks everyone, Daniel

bpf-next is OPEN

Merge window is closed, so new round begins as usual. Thanks everyone, Daniel

Re: bpf-next is OPEN

On 03/19/2019 06:01 PM, Alban Crequy wrote: > On Tue, 19 Mar 2019 at 09:56, Daniel Borkmann wrote: >> >> Merge window is closed, so new round begins. >> >> Thanks everyone, >> Daniel > > Thanks! I see that the bpf tree is more recent than the bpf-next tree: > https://git.kernel.org/?q=BPF+Group >

Re: bpf-next is OPEN

On Tue, 19 Mar 2019 at 09:56, Daniel Borkmann wrote: > > Merge window is closed, so new round begins. > > Thanks everyone, > Daniel Thanks! I see that the bpf tree is more recent than the bpf-next tree: https://git.kernel.org/?q=BPF+Group Does it need to be updated, or do I miss something? Chee

bpf-next is OPEN

Merge window is closed, so new round begins. Thanks everyone, Daniel

bpf-next is OPEN

Fyi, now that net-next is open, bpf-next is back open as well. Thanks, Daniel

bpf-next is OPEN

Merge window is over so bpf-next is open again! Thanks, Daniel

bpf-next is OPEN

Merge window is over so new bpf-next development round begins. Thanks, Daniel

bpf-next is OPEN

Merge window is over so new bpf-next development round begins. Due to travel this whole week till this Sun mostly offline, but feel free to push your patches out already so they land in patchwork meanwhile.

bpf-next is OPEN

Merge window is over so new bpf-next development round begins.

bpf-next is OPEN

Given the merge window is over, feel free to shoot your patches out to bpf-next tree. Thanks, Daniel