Hi Alexei,
On Mon, 12 Oct 2020 14:03:07 -0700 Alexei Starovoitov
wrote:
>
> That is a great idea! I think that should work well for everyone.
> Let's do exactly that.
> Just pushed bpf-next/for-next branch.
From now on I will only fetch the for-next branch.
Thanks.
--
Cheers,
Stephen Rothwell
On 10/12/20 11:03 PM, Alexei Starovoitov wrote:
On Tue, Oct 13, 2020 at 07:50:16AM +1100, Stephen Rothwell wrote:
[...]
How about this: you create a for-next branch in the bpf-next tree and I
fetch that instead of your master branch. What you do is always work
in your master branch and wheneve
On Tue, Oct 13, 2020 at 07:50:16AM +1100, Stephen Rothwell wrote:
> Hi Alexei,
>
> On Mon, 12 Oct 2020 13:15:16 -0700 Alexei Starovoitov
> wrote:
> >
> > You mean keep pushing into bpf-next/master ?
> > The only reason is linux-next.
> > But coming to think about it again, let's fix linux-next p
Hi Alexei,
On Mon, 12 Oct 2020 13:15:16 -0700 Alexei Starovoitov
wrote:
>
> You mean keep pushing into bpf-next/master ?
> The only reason is linux-next.
> But coming to think about it again, let's fix linux-next process instead.
>
> Stephen,
> could you switch linux-next to take from bpf.git d
On Mon, Oct 12, 2020 at 11:00 AM Jakub Kicinski wrote:
>
> On Sun, 11 Oct 2020 17:59:16 -0700 Alexei Starovoitov wrote:
> > Hi BPF developers,
> >
> > The merge window has just opened.
> > Which would typically mean that bpf-next is closing,
> > but things are going to be a little bit different th
On Sun, 11 Oct 2020 17:59:16 -0700 Alexei Starovoitov wrote:
> Hi BPF developers,
>
> The merge window has just opened.
> Which would typically mean that bpf-next is closing,
> but things are going to be a little bit different this time.
> We're stopping to accept new features into bpf-next/master
