From: mingo@kernel•org (Ingo Molnar)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] efi/arm64: don't apply MEMBLOCK_NOMAP to UEFI memory map mapping
Date: Sat, 16 Apr 2016 11:09:10 +0200 [thread overview]
Message-ID: <20160416090910.GA30739@gmail.com> (raw)
In-Reply-To: <20160415221516.GU2829@codeblueprint.co.uk>
* Matt Fleming <matt@codeblueprint•co.uk> wrote:
> On Fri, 15 Apr, at 05:44:02PM, Steve Capper wrote:
> >
> > Hello,
> > Is this going to make it in for 4.6?
> > I ran into this issue the other day, and can confirm that Ard's patch
> > is helpful.
>
> Good question.
>
> Ingo did you send the patch in the last EFI urgent pull request to
> Linus yet? I can find it in tip/efi-urgent-for-linus but not in Linus'
> tree.
I just sent it to Linus.
It got delayed a bit because it had an x86/urgent dependency that had to be sent
upstream first. (In the future you can avoid such delays by basing EFI urgent
fixes on an upstream -rc kernel, not x86/urgent.)
Thanks,
Ingo
next prev parent reply other threads:[~2016-04-16 9:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 7:46 [PATCH] efi/arm64: don't apply MEMBLOCK_NOMAP to UEFI memory map mapping Ard Biesheuvel
2016-03-31 10:53 ` Will Deacon
2016-03-31 20:35 ` Matt Fleming
2016-04-15 16:44 ` Steve Capper
2016-04-15 22:15 ` Matt Fleming
2016-04-16 9:09 ` Ingo Molnar [this message]
2016-04-16 10:27 ` Matt Fleming
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=20160416090910.GA30739@gmail.com \
--to=mingo@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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