From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Mickaël Salaün" <mic@digikod.net>,
"Ricky Zhou" <rickyz@chromium.org>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [GIT PULL] seccomp fixes for v4.9-rc4
Date: Sat, 5 Nov 2016 03:35:10 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.20.1611050334550.16440@namei.org> (raw)
In-Reply-To: <CAGXu5jKYBnjkTpuO9xeJw2gRya=7V3x-R53MBYG8x_7jrK5m=g@mail.gmail.com>
On Tue, 1 Nov 2016, Kees Cook wrote:
> > How about we queue this up for 4.10?
>
> Okay, sounds good to me. Thanks!
Pulled to -next.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2016-11-04 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 17:46 [GIT PULL] seccomp fixes for v4.9-rc4 Kees Cook
2016-11-01 22:43 ` James Morris
2016-11-02 2:07 ` Kees Cook
2016-11-04 16:35 ` James Morris [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=alpine.LRH.2.20.1611050334550.16440@namei.org \
--to=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mic@digikod.net \
--cc=rickyz@chromium.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;
as well as URLs for NNTP newsgroup(s).