From: Matt Fleming <matt@codeblueprint.co.uk>
To: fupan.li@windriver.com
Cc: gregkh@linuxfoundation.org, jslaby@suse.cz,
linux-efi@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, fupanli@gmail.com,
ben@decadent.org.uk
Subject: Re: [PATCH V3 request from stable 3.10 to 3.14] efi: fix 32bit kernel boot failed problem using efi
Date: Tue, 4 Aug 2015 18:12:56 +0100 [thread overview]
Message-ID: <20150804171256.GA4332@codeblueprint.co.uk> (raw)
In-Reply-To: <1438653081-25746-1-git-send-email-fupan.li@windriver.com>
On Tue, 04 Aug, at 09:51:21AM, fupan.li@windriver.com wrote:
> From: Fupan Li <fupan.li@windriver.com>
>
> Commit 35d5134b7d5a
> ("x86/efi: Correct EFI boot stub use of code32_start")
> imported a bug, which will cause 32bit kernel boot failed
> using efi method. It should use the label's address instead
> of the value stored in the label to caculate the address of
> code32_start.
>
> Signed-off-by: Fupan Li <fupan.li@windriver.com>
> ---
> arch/x86/boot/compressed/head_32.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Matt Fleming <matt.fleming@intel.com>
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2015-08-04 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 1:51 [PATCH V3 request from stable 3.10 to 3.14] efi: fix 32bit kernel boot failed problem using efi fupan.li
2015-08-04 17:12 ` Matt Fleming [this message]
2015-08-08 22:05 ` Patch "efi: fix 32bit kernel boot failed problem using efi" has been added to the 3.10-stable tree gregkh
2015-08-08 22:05 ` Patch "efi: fix 32bit kernel boot failed problem using efi" has been added to the 3.14-stable tree gregkh
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=20150804171256.GA4332@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=ben@decadent.org.uk \
--cc=fupan.li@windriver.com \
--cc=fupanli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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).