From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kees Cook <keescook@chromium•org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Eric Biederman <ebiederm@xmission•com>,
Andrew Morton <akpm@linux-foundation•org>,
linux-mm@kvack•org
Subject: Re: Please add for-next/execve
Date: Mon, 28 Feb 2022 08:19:34 +1100 [thread overview]
Message-ID: <20220228081934.1b5bc274@canb.auug.org.au> (raw)
In-Reply-To: <202202232131.809767F@keescook>
[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]
Hi Kees,
On Wed, 23 Feb 2022 21:37:51 -0800 Kees Cook <keescook@chromium•org> wrote:
>
> As part of Eric and I stepping up to officially[1] be the execve and
> binfmt maintainers, please add my for-next/execve tree to linux-next:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/log/?h=for-next/execve
>
> This tree currently contains all the exec and binfmt patches from mmotm
> as well as at least one newly reviewed change[2].
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/MAINTAINERS?h=v5.17-rc1#n7223
> [2] https://lore.kernel.org/lkml/164486710836.287496.5467210321357577186.b4-ty@chromium.org/
Added from today (Mark added it earlier to his tree).
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
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2022-02-27 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 5:37 Please add for-next/execve Kees Cook
2022-02-24 20:20 ` Matthew Wilcox
2022-02-25 2:22 ` Mark Brown
2022-02-27 21:19 ` 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=20220228081934.1b5bc274@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=ebiederm@xmission$(echo .)com \
--cc=keescook@chromium$(echo .)org \
--cc=linux-mm@kvack$(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