please add for-next/seccomp

please add for-next/seccomp

[Kees Cook]

Hi Stephen,

Can you please add my "for-next/seccomp" tree to linux-next? I've been
including it in the already added "for-next/kspp" tree, but I'd rather
have it be its own tree for linux-next, as it is ultimately its own topic.

https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/seccomp

Thanks!

-Kees

-- 
Kees Cook

Re: please add for-next/seccomp

[Stephen Rothwell]

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

Hi Kees,

On Thu, 18 Jun 2020 14:00:44 -0700 Kees Cook <keescook@chromium.org> wrote:
>
> Can you please add my "for-next/seccomp" tree to linux-next? I've been
> including it in the already added "for-next/kspp" tree, but I'd rather
> have it be its own tree for linux-next, as it is ultimately its own topic.
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/seccomp

I have added

git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git branch for-next/seccomp

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 --]