From: David Howells <dhowells@redhat.com>
To: sfr@canb.auug.org.au
Cc: dhowells@redhat.com, jmorris@namei.org,
ard.biesheuvel@linaro.org, jforbes@redhat.com, mjg59@google.com,
linux-security-module@vger.kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, mtk.manpages@gmail.com
Subject: Re: linux-next: UEFI Secure boot lockdown patchset
Date: Thu, 01 Mar 2018 11:24:39 +0000 [thread overview]
Message-ID: <7296.1519903479@warthog.procyon.org.uk> (raw)
In-Reply-To: <26787.1519902415@warthog.procyon.org.uk>
I forgot to include the branch URL:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=efi-lock-down
Thanks for spotting that, Ard!
David
WARNING: multiple messages have this Message-ID (diff)
From: dhowells@redhat.com (David Howells)
To: linux-security-module@vger.kernel.org
Subject: linux-next: UEFI Secure boot lockdown patchset
Date: Thu, 01 Mar 2018 11:24:39 +0000 [thread overview]
Message-ID: <7296.1519903479@warthog.procyon.org.uk> (raw)
In-Reply-To: <26787.1519902415@warthog.procyon.org.uk>
I forgot to include the branch URL:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=efi-lock-down
Thanks for spotting that, Ard!
David
--
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:[~2018-03-01 11:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 11:06 linux-next: UEFI Secure boot lockdown patchset David Howells
2018-03-01 11:06 ` David Howells
2018-03-01 11:08 ` Ard Biesheuvel
2018-03-01 11:08 ` Ard Biesheuvel
2018-03-01 11:24 ` David Howells [this message]
2018-03-01 11:24 ` David Howells
2018-03-01 12:15 ` Stephen Rothwell
2018-05-01 17:28 ` Matthew Garrett
2018-05-01 19:00 ` David Howells
2018-05-01 20:15 ` Mimi Zohar
2018-05-01 21:02 ` Matthew Garrett
2018-05-01 21:50 ` Mimi Zohar
2018-05-01 21:59 ` Matthew Garrett
2018-05-01 22:21 ` Mimi Zohar
2018-05-01 22:32 ` Matthew Garrett
2018-05-01 23:43 ` Mimi Zohar
2018-05-01 23:46 ` Matthew Garrett
2018-05-02 1:00 ` Mimi Zohar
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=7296.1519903479@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=jforbes@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mjg59@google.com \
--cc=mtk.manpages@gmail.com \
--cc=sfr@canb.auug.org.au \
/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.