All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: David Howells <dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org,
	linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [GIT PULL] efi: Pass secure boot mode to kernel
Date: Thu, 8 Dec 2016 11:56:52 +0000	[thread overview]
Message-ID: <20161208115652.GE5462@codeblueprint.co.uk> (raw)
In-Reply-To: <4561.1481197517-S6HVgzuS8uM4Awkfq6JHfwNdhmdF6hFW@public.gmane.org>

On Thu, 08 Dec, at 11:45:17AM, David Howells wrote:
> Hi Matt, Ard,
> 
> Is it too late to request this for the upcoming merge window?

For something as non-trivial as this, yes, it's too late. We generally
close the EFI tree window for new features around -rc5 time.

> Also, I've made
> Lukas's requested changes and reposted just that patch in my reply to him.  Do
> you want me to repost the lot?
 
Please do, yeah.

WARNING: multiple messages have this Message-ID (diff)
From: matt@codeblueprint.co.uk (Matt Fleming)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] efi: Pass secure boot mode to kernel
Date: Thu, 8 Dec 2016 11:56:52 +0000	[thread overview]
Message-ID: <20161208115652.GE5462@codeblueprint.co.uk> (raw)
In-Reply-To: <4561.1481197517@warthog.procyon.org.uk>

On Thu, 08 Dec, at 11:45:17AM, David Howells wrote:
> Hi Matt, Ard,
> 
> Is it too late to request this for the upcoming merge window?

For something as non-trivial as this, yes, it's too late. We generally
close the EFI tree window for new features around -rc5 time.

> Also, I've made
> Lukas's requested changes and reposted just that patch in my reply to him.  Do
> you want me to repost the lot?
 
Please do, yeah.

WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: David Howells <dhowells@redhat.com>
Cc: 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: Thu, 8 Dec 2016 11:56:52 +0000	[thread overview]
Message-ID: <20161208115652.GE5462@codeblueprint.co.uk> (raw)
In-Reply-To: <4561.1481197517@warthog.procyon.org.uk>

On Thu, 08 Dec, at 11:45:17AM, David Howells wrote:
> Hi Matt, Ard,
> 
> Is it too late to request this for the upcoming merge window?

For something as non-trivial as this, yes, it's too late. We generally
close the EFI tree window for new features around -rc5 time.

> Also, I've made
> Lukas's requested changes and reposted just that patch in my reply to him.  Do
> you want me to repost the lot?
 
Please do, yeah.

  parent reply	other threads:[~2016-12-08 11:56 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 [this message]
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
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=20161208115652.GE5462@codeblueprint.co.uk \
    --to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
    --cc=ard.biesheuvel-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=dhowells-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.