grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Lukas Wunner <lukas@wunner.de>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Andreas Noever <andreas.noever@gmail.com>,
	grub-devel@gnu.org, x86@kernel.org,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH v2 0/4] Apple device properties
Date: Tue, 13 Sep 2016 12:29:21 +0100	[thread overview]
Message-ID: <20160913112921.GH3872@codeblueprint.co.uk> (raw)
In-Reply-To: <cover.1473242067.git.lukas@wunner.de>

On Wed, 07 Sep, at 12:49:18PM, Lukas Wunner wrote:
> Retrieve device properties from EFI on Macs before ExitBootServices is
> called and assign them to devices (patch [3/4]). The devices that
> properties pertain to are encoded as EFI Device Paths, so add a parser
> for these (patch [2/4]). As a first use case, amend the Thunderbolt driver
> to take advantage of the Device ROM supplied by EFI (patch [4/4]).
> 
> Patch [1/4] is already queued in Rafael J. Wysocki's tree for 4.9 and is
> included here only because patch [2/4] wouldn't compile without it.
> 
> The series also depends on these two patches which are already queued
> in Matt's tree for 4.9:
> 
> - x86/efi: Optimize away setup_gop32/64 if unused
>   https://patchwork.kernel.org/patch/9315763/
> 
> - x86/efi: Allow invocation of arbitrary boot services
>   https://patchwork.kernel.org/patch/9293371/

I had a quick look over these series and nothing looks too crazy, but
I still need to do an in-depth review.

Given the patch dependencies you outlined above, could you resubmit
this after the v4.9 merge window closes? That way it won't be
forgotten about.


      parent reply	other threads:[~2016-09-13 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07 10:49 [PATCH v2 0/4] Apple device properties Lukas Wunner
2016-09-07 10:49 ` [PATCH v2 3/4] x86/efi: Retrieve and assign " Lukas Wunner
2016-09-13 11:29 ` Matt Fleming [this message]

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=20160913112921.GH3872@codeblueprint.co.uk \
    --to=matt@codeblueprint.co.uk \
    --cc=andreas.noever@gmail.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=grub-devel@gnu.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=x86@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).