From: yannik@sembritzki.me (Yannik Sembritzki)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 1/2] Replace magic for trusting the secondary keyring with #define
Date: Thu, 16 Aug 2018 15:17:47 +0200 [thread overview]
Message-ID: <07e17009-18bb-df72-3408-7e8c0c11e16f@sembritzki.me> (raw)
In-Reply-To: <18610.1534425319@warthog.procyon.org.uk>
On 16.08.2018 15:15, David Howells wrote:
> I would suggest something like that. I've switched the patches over as has
> been suggested. I think it makes more sense to create the constant first and
> then use that.
>
> I've also fleshed out the patch description a bit and added cc and Fixes
> fields as appropriate.
Thanks, that looks good to me.
I see that you only cc'd stable@ in the (now) second patch. I'm curious,
will this automatically apply the first patch to stable?
Yannik
next prev parent reply other threads:[~2018-08-16 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 13:05 [PATCH 1/2] Replace magic for trusting the secondary keyring with #define David Howells
2018-08-16 13:05 ` [PATCH 2/2] Fix kexec forbidding kernels signed with keys in the secondary keyring to boot David Howells
2018-08-16 13:15 ` [PATCH 1/2] Replace magic for trusting the secondary keyring with #define David Howells
2018-08-16 13:17 ` Yannik Sembritzki [this message]
2018-08-16 15:12 ` Greg KH
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=07e17009-18bb-df72-3408-7e8c0c11e16f@sembritzki.me \
--to=yannik@sembritzki.me \
--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 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).