From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Oleg Nesterov <oleg@redhat.com>, Will Drewry <wad@chromium.org>,
Julien Tinnes <jln@chromium.org>,
David Drysdale <drysdale@google.com>
Subject: Re: [PULL] seccomp update (3.17)
Date: Sat, 19 Jul 2014 17:36:46 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.11.1407191736250.26264@namei.org> (raw)
In-Reply-To: <20140718191908.GA20534@www.outflux.net>
On Fri, 18 Jul 2014, Kees Cook wrote:
> Hi James,
>
> Please pull these seccomp changes for 3.17.
>
Pulled, thanks.
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2014-07-19 7:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 19:19 Kees Cook
2014-07-19 6:16 ` Theodore Ts'o
2014-07-19 14:49 ` Kees Cook
2014-07-19 21:50 ` Theodore Ts'o
2014-07-19 7:36 ` 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.11.1407191736250.26264@namei.org \
--to=jmorris@namei.org \
--cc=drysdale@google.com \
--cc=jln@chromium.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=wad@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
all inboxes | Powered by JetHome®