From: James Morris <jmorris@namei.org>
To: Kees Cook <keescook@chromium.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] seccomp updates for next
Date: Tue, 27 Jun 2017 13:27:49 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1706271327340.11229@namei.org> (raw)
In-Reply-To: <20170626170205.GA108402@beast>
On Mon, 26 Jun 2017, Kees Cook wrote:
> Hi James,
>
> Please pull these seccomp changes for next. These are all tiny changes,
> but I got delayed sending them to you. I'd like have these land for v4.13;
> I should have sent them for v4.12. :P
Pulled to -next, thanks.
--
James Morris
<jmorris@namei.org>
WARNING: multiple messages have this Message-ID (diff)
From: jmorris@namei.org (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [GIT PULL] seccomp updates for next
Date: Tue, 27 Jun 2017 13:27:49 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.20.1706271327340.11229@namei.org> (raw)
In-Reply-To: <20170626170205.GA108402@beast>
On Mon, 26 Jun 2017, Kees Cook wrote:
> Hi James,
>
> Please pull these seccomp changes for next. These are all tiny changes,
> but I got delayed sending them to you. I'd like have these land for v4.13;
> I should have sent them for v4.12. :P
Pulled to -next, thanks.
--
James Morris
<jmorris@namei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-06-27 3:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 17:02 [GIT PULL] seccomp updates for next Kees Cook
2017-06-26 17:02 ` Kees Cook
2017-06-27 3:27 ` James Morris [this message]
2017-06-27 3:27 ` James Morris
2017-08-15 22:03 Kees Cook
2017-08-15 22:03 ` Kees Cook
2017-08-16 2:33 ` James Morris
2017-08-16 2:33 ` James Morris
2017-11-29 0:38 Kees Cook
2017-11-29 0:38 ` Kees Cook
2017-11-29 1:55 ` James Morris
2017-11-29 1:55 ` James Morris
2018-12-12 23:16 Kees Cook
2018-12-13 0:08 ` 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=alpine.LRH.2.20.1706271327340.11229@namei.org \
--to=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.