From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kees Cook <keescook@chromium•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: Re: please add for-next/seccomp
Date: Mon, 22 Jun 2020 07:27:08 +1000 [thread overview]
Message-ID: <20200622072708.14742b70@canb.auug.org.au> (raw)
In-Reply-To: <202006181357.5664DBCD4D@keescook>
[-- 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 --]
prev parent reply other threads:[~2020-06-21 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 21:00 please add for-next/seccomp Kees Cook
2020-06-21 21:27 ` Stephen Rothwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200622072708.14742b70@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=keescook@chromium$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox