From: Kees Cook <keescook@chromium.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: please add for-next/seccomp
Date: Thu, 18 Jun 2020 14:00:44 -0700 [thread overview]
Message-ID: <202006181357.5664DBCD4D@keescook> (raw)
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
next reply other threads:[~2020-06-18 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 21:00 Kees Cook [this message]
2020-06-21 21:27 ` please add for-next/seccomp 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=202006181357.5664DBCD4D@keescook \
--to=keescook@chromium.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;
as well as URLs for NNTP newsgroup(s).