linux-next: add apparmor-next tree

linux-next: add apparmor-next tree

[John Johansen]

Hi Stephan,

can you please add apparmor-next from

git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor#apparmor-next

to the linux-next tree

I have run through a test merge, build, and set of regression tests against the March 13 tree without any issues.

thanks
- John

Re: linux-next: add apparmor-next tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]

Hi John,

On Tue, 13 Mar 2018 23:47:04 -0700 John Johansen <john.johansen@canonical.com> wrote:
>
> can you please add apparmor-next from
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jj/linux-apparmor#apparmor-next
> 
> to the linux-next tree
> 
> I have run through a test merge, build, and set of regression tests against the March 13 tree without any issues.

Added from today.

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 
sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]