Re: bpf trees integration for linux-next

[Daniel Borkmann]

On 11/28/2017 11:52 PM, Stephen Rothwell wrote:
[...]
> Added from today.  I used the master branch in each case. You might
> consider adding your trees to the MAINTAINERS file.

Great, thanks Stephen! Yep, we'll do a doc update round some time
this week.

> Thanks for adding your subsystem tree as a participant of linux-next.  As
> you may know, this is not a judgement of your code.  The purpose of
> linux-next is for integration testing and to lower the impact of
> conflicts between subsystems in the next merge window. 
> 
> You will need to ensure that the patches/commits in your tree/series have
> been:
>  * submitted under GPL v2 (or later) and include the Contributor's
> Signed-off-by,
>  * posted to the relevant mailing list,
>  * reviewed by you (or another maintainer of your subsystem tree),
>  * successfully unit tested, and 
>  * destined for the current or next Linux merge window.
> 
> Basically, this should be just what you would send to Linus (or ask him
> to fetch).  It is allowed to be rebased if you deem it necessary.

Well aware.

Thanks a lot,
Daniel

Re: bpf trees integration for linux-next

[Stephen Rothwell]

Hi Daniel,

On Tue, 28 Nov 2017 16:33:00 +0100 Daniel Borkmann  wrote:
>
> Alexei (Cc) and myself are maintaining the bpf and bpf-next tree for
> upstream:
> 
>https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/
>https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/
> 
> Is it possible that you could integrate the two into linux-next as
> well, that would help us a lot with regards to being aware of conflicts
> with any other trees. The BPF trees are usually pulled into net and
> net-next by David S. Miller.
> 
> Patches are coming in via netdev@vger.kernel.org list as well, so it
> would be great if possible if notifications could Cc netdev@vger.kernel.org
> and Alexei and myself.

Added from today.  I used the master branch in each case. You might
consider adding your trees to the MAINTAINERS file.

Thanks for adding your subsystem tree as a participant of linux-next.  As
you may know, this is not a judgement of your code.  The purpose of
linux-next is for integration testing and to lower the impact of
conflicts between subsystems in the next merge window. 

You will need to ensure that the patches/commits in your tree/series have
been:
 * submitted under GPL v2 (or later) and include the Contributor's
Signed-off-by,
 * posted to the relevant mailing list,
 * reviewed by you (or another maintainer of your subsystem tree),
 * successfully unit tested, and 
 * destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him
to fetch).  It is allowed to be rebased if you deem it necessary.

-- 
Cheers,
Stephen Rothwell 
s...@canb.auug.org.au