From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, Olof Johansson <olof@lixom.net>
Subject: [PULL] seccomp update (next)
Date: Thu, 7 Jul 2016 10:59:47 -0700 [thread overview]
Message-ID: <20160707175947.GA19305@www.outflux.net> (raw)
Hi,
Please pull these seccomp changes for next.
Thanks!
-Kees
The following changes since commit d011a4d861ce583466a8ae72a0c8e7f51c8cba4e:
Merge branch 'stable-4.8' of git://git.infradead.org/users/pcmoore/selinux into next (2016-07-07 10:15:34 +1000)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/seccomp-next
for you to fetch changes up to f6041c1d8a0825e41219a0443d365318d238d7b3:
samples/seccomp: Add standalone config option (2016-07-07 10:58:03 -0700)
----------------------------------------------------------------
Seccomp samples building fix
----------------------------------------------------------------
Olof Johansson (1):
samples/seccomp: Add standalone config option
samples/Kconfig | 7 +++++++
samples/seccomp/Makefile | 2 +-
2 files changed, 8 insertions(+), 1 deletion(-)
--
Kees Cook
Chrome OS & Brillo Security
next reply other threads:[~2016-07-07 17:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 17:59 Kees Cook [this message]
2016-07-07 23:47 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2016-06-14 17:57 Kees Cook
2016-06-17 7:15 ` James Morris
2016-06-17 18:55 ` Andy Lutomirski
2016-06-18 7:02 ` Kees Cook
2016-06-18 10:21 ` Andy Lutomirski
2016-06-19 22:45 ` Andy Lutomirski
2016-01-05 23:40 Kees Cook
2015-07-15 18:56 Kees Cook
2015-07-20 6:58 ` James Morris
2014-11-25 19:43 Kees Cook
2014-11-26 13:23 ` James Morris
2014-11-26 21:46 ` Stephen Rothwell
2014-11-26 21:59 ` Kees Cook
2014-11-27 23:37 ` James Morris
2014-12-01 20:34 ` Kees Cook
2014-12-01 22:56 ` James Morris
2014-12-01 23:06 ` Kees Cook
2014-12-02 7:56 ` James Morris
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=20160707175947.GA19305@www.outflux.net \
--to=keescook@chromium.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=olof@lixom.net \
/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®