From: Matt Fleming <matt@codeblueprint.co.uk>
To: joeyli <jlee@suse.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Matt Fleming <matt.fleming@intel.com>,
Borislav Petkov <bp@suse.de>,
Leif Lindholm <leif.lindholm@linaro.org>,
Peter Jones <pjones@redhat.com>,
James Bottomley <JBottomley@Odin.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
"H. Peter Anvin" <hpa@zytor.com>, Dave Young <dyoung@redhat.com>,
stable@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: Re: [PATCH] x86/efi: Map EFI memmap entries in-order at runtime
Date: Tue, 8 Sep 2015 21:41:47 +0100 [thread overview]
Message-ID: <20150908204147.GC2854@codeblueprint.co.uk> (raw)
In-Reply-To: <20150907040752.GW13182@linux-rxt1.site>
On Mon, 07 Sep, at 12:07:52PM, joeyli wrote:
>
> This patch works to me on Intel S1200V3RPS to fix issue:
> DMI: Intel Corporation (uefidk.com) Intel Server Board S1200V3RPS UEFI Development Kit/ROMLEY, BIOS 2.0
>
> Tested-by: Lee, Chun-Yi <jlee@suse.com>
When you say "fix issue", do you mean that your machine has the
EFI_PROPERTIES_TABLE feature enabled, and that it doesn't boot without
this patch?
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-09-08 20:41 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-04 13:14 [PATCH] x86/efi: Map EFI memmap entries in-order at runtime Matt Fleming
2015-09-04 13:24 ` Ard Biesheuvel
[not found] ` <CAKv+Gu9bGcSVWuMkPVJGDkCPmWvFpjhh4odLWPBZ-wX3=LgGaw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-04 18:23 ` Matt Fleming
2015-09-04 18:53 ` Ard Biesheuvel
2015-09-06 14:06 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-AQdgJNOtrgtEtqxsaSC_L=EANpC3pT8b6X2jmZ5qO_Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-08 13:16 ` Matt Fleming
2015-09-08 13:21 ` Ard Biesheuvel
[not found] ` <CAKv+Gu_us3Nu_gMd4GxPe7z0eqtMfM4DM_UEmGW2MTqVDxg5vA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-08 20:37 ` Matt Fleming
[not found] ` <20150908203630.GB2854-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-09-09 7:37 ` Ard Biesheuvel
2015-09-09 9:58 ` Matt Fleming
[not found] ` <20150909095806.GA4973-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-09-09 9:59 ` Ard Biesheuvel
[not found] ` <1441372447-23439-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-09-07 4:07 ` joeyli
2015-09-08 20:41 ` Matt Fleming [this message]
2015-09-09 0:33 ` joeyli
2015-09-09 11:21 ` Matt Fleming
[not found] ` <20150909112123.GB4973-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-09-10 3:38 ` joeyli
2015-09-16 10:08 ` Borislav Petkov
[not found] ` <20150916100820.GA7077-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-09-16 11:25 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-Q_g4YtbZ7X1S1g3RaMZC6HQCVza+oqv26mXbrDjTc5w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-09-16 13:28 ` Borislav Petkov
2015-09-16 13:38 ` Ard Biesheuvel
2015-09-17 8:05 ` Borislav Petkov
2015-09-16 13:37 ` James Bottomley
2015-09-16 14:07 ` Ard Biesheuvel
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=20150908204147.GC2854@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=JBottomley@Odin.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@suse.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=jlee@suse.com \
--cc=leif.lindholm@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=pjones@redhat.com \
--cc=stable@vger.kernel.org \
--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).