From: Mark Brown <broonie@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Kees Cook <keescook@chromium.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
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: Fri, 25 Feb 2022 02:22:54 +0000 [thread overview]
Message-ID: <Yhg9fkjX5s2xX2/y@sirena.org.uk> (raw)
In-Reply-To: <YhfoqF8nj7lQxGDe@casper.infradead.org>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
On Thu, Feb 24, 2022 at 08:20:56PM +0000, Matthew Wilcox wrote:
> On Wed, Feb 23, 2022 at 09:37:51PM -0800, Kees Cook 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].
> Hey Kees, Stephen's on holiday this week. Mark's stepping into his
> shoes for another couple of days.
I'll give importing this ago tomorrow for my final attempt of the week
at -next, you should make sure that Stephen picks it up when he gets
back though.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-25 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 5:37 Kees Cook
2022-02-24 20:20 ` Matthew Wilcox
2022-02-25 2:22 ` Mark Brown [this message]
2022-02-27 21:19 ` Stephen Rothwell
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=Yhg9fkjX5s2xX2/y@sirena.org.uk \
--to=broonie@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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