From: James Morris <james.l.morris@oracle.com>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: David Howells <dhowells@redhat.com>,
linux-integrity <linux-integrity@vger.kernel.org>,
Matthew Garrett <mjg59@google.com>,
linux-security-module <linux-security-module@vger.kernel.org>
Subject: Re: [RFC PATCH] ima: require secure_boot rules in lockdown mode
Date: Tue, 31 Oct 2017 14:25:26 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1710311424310.22021@localhost> (raw)
In-Reply-To: <1509385178.3583.159.camel@linux.vnet.ibm.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: multipart/mixed; BOUNDARY="8323328-984484137-1509420330=:22021", Size: 376 bytes --]
On Mon, 30 Oct 2017, Mimi Zohar wrote:
> James is staging the subsystem patches independently of each other, in
> case of a similar problem, so that they can be pulled separately.
> There's a new "next-general" branch.
If you send me a pull request, I'm combining branches into next-testing,
too, which is pulled into -next.
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-10-31 3:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 15:59 [RFC PATCH] ima: require secure_boot rules in lockdown mode Mimi Zohar
2017-10-30 15:55 ` David Howells
2017-10-30 17:00 ` Mimi Zohar
2017-10-30 17:05 ` David Howells
2017-10-30 17:39 ` Mimi Zohar
2017-10-31 3:25 ` James Morris [this message]
2017-11-08 20:46 ` Mimi Zohar
2017-11-08 20:53 ` Stephen Rothwell
2017-11-08 21:04 ` Mimi Zohar
2017-11-08 23:26 ` Stephen Rothwell
2017-11-09 3:06 ` Mimi Zohar
2017-11-09 13:28 ` James Morris
2017-11-09 13:46 ` Mimi Zohar
2017-11-09 19:17 ` James Morris
2017-11-02 17:11 ` David Howells
2017-11-02 21:30 ` Mimi Zohar
2017-11-02 21:43 ` David Howells
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.LFD.2.20.1710311424310.22021@localhost \
--to=james.l.morris@oracle.com \
--cc=dhowells@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.com \
--cc=zohar@linux.vnet.ibm.com \
/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).