From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Please add for-next/execve
Date: Wed, 23 Feb 2022 21:37:51 -0800 [thread overview]
Message-ID: <202202232131.809767F@keescook> (raw)
Hello!
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/
--
Kees Cook
next reply other threads:[~2022-02-24 5:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 5:37 Kees Cook [this message]
2022-02-24 20:20 ` Matthew Wilcox
2022-02-25 2:22 ` Mark Brown
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=202202232131.809767F@keescook \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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