From: David Howells <dhowells@redhat.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: linux-efi@vger.kernel.org, ard.biesheuvel@linaro.org,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] efi: Pass secure boot mode to kernel
Date: Mon, 09 Jan 2017 10:40:09 +0000 [thread overview]
Message-ID: <2696.1483958409@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170109101547.GE16838@codeblueprint.co.uk>
Matt Fleming <matt@codeblueprint.co.uk> wrote:
> > Can I request that it be pulled now? Are you going to update efi/core?
>
> Sorry for the delay David. I've just returned from annual leave and
> I'll take a look at this series this week.
That's okay, thanks!
David
WARNING: multiple messages have this Message-ID (diff)
From: dhowells@redhat.com (David Howells)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] efi: Pass secure boot mode to kernel
Date: Mon, 09 Jan 2017 10:40:09 +0000 [thread overview]
Message-ID: <2696.1483958409@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170109101547.GE16838@codeblueprint.co.uk>
Matt Fleming <matt@codeblueprint.co.uk> wrote:
> > Can I request that it be pulled now? Are you going to update efi/core?
>
> Sorry for the delay David. I've just returned from annual leave and
> I'll take a look at this series this week.
That's okay, thanks!
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: dhowells@redhat.com, ard.biesheuvel@linaro.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] efi: Pass secure boot mode to kernel
Date: Mon, 09 Jan 2017 10:40:09 +0000 [thread overview]
Message-ID: <2696.1483958409@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170109101547.GE16838@codeblueprint.co.uk>
Matt Fleming <matt@codeblueprint.co.uk> wrote:
> > Can I request that it be pulled now? Are you going to update efi/core?
>
> Sorry for the delay David. I've just returned from annual leave and
> I'll take a look at this series this week.
That's okay, thanks!
David
next prev parent reply other threads:[~2017-01-09 10:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 11:45 [GIT PULL] efi: Pass secure boot mode to kernel David Howells
2016-12-08 11:45 ` David Howells
2016-12-08 11:45 ` David Howells
[not found] ` <4561.1481197517-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>
2016-12-08 11:56 ` Matt Fleming
2016-12-08 11:56 ` Matt Fleming
2016-12-08 11:56 ` Matt Fleming
[not found] ` <20161208115652.GE5462-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2017-01-05 14:41 ` David Howells
2017-01-05 14:41 ` David Howells
2017-01-05 14:41 ` David Howells
2017-01-09 10:15 ` Matt Fleming
2017-01-09 10:15 ` Matt Fleming
2017-01-09 10:15 ` Matt Fleming
2017-01-09 10:40 ` David Howells [this message]
2017-01-09 10:40 ` David Howells
2017-01-09 10:40 ` 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=2696.1483958409@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
/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.