From: Matt Fleming <matt@codeblueprint.co.uk>
To: fupan.li@windriver.com
Cc: linux-kernel@vger.kernel.org, fupanli@gmail.com,
linux-efi@vger.kernel.org,
Luis Henriques <luis.henriques@canonical.com>,
Greg KH <gregkh@linuxfoundation.org>,
stable@vger.kernel.org
Subject: Re: [PATCH 3.10 ~ 3.14] efi: fix the efi 32bit boot failed problem
Date: Thu, 30 Jul 2015 16:04:28 +0100 [thread overview]
Message-ID: <20150730150428.GJ2725@codeblueprint.co.uk> (raw)
In-Reply-To: <1438078879-24705-1-git-send-email-fupan.li@windriver.com>
(Add linux-efi, Luis and Greg)
On Tue, 28 Jul, at 06:21:19PM, fupan.li@windriver.com wrote:
> From: fli <fupan.li@windriver.com>
>
> The commit 35d5134b7d5a55e269c953096224248b9f6f72c2
> Author: Matt Fleming <matt@console-pimps.org>
> Date: Tue Apr 8 13:14:00 2014 +0100
>
> x86/efi: Correct EFI boot stub use of code32_start
>
> imported a bug, which should use the label's address instead
> of the value stored in the label's address to caculate the
> code32_start address.
>
> Signed-off-by: fli <fupan.li@windriver.com>
> ---
> arch/x86/boot/compressed/head_32.S | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/boot/compressed/head_32.S b/arch/x86/boot/compressed/head_32.S
> index abb988a..3b28eff 100644
> --- a/arch/x86/boot/compressed/head_32.S
> +++ b/arch/x86/boot/compressed/head_32.S
> @@ -54,7 +54,7 @@ ENTRY(efi_pe_entry)
> call reloc
> reloc:
> popl %ecx
> - subl reloc, %ecx
> + subl $reloc, %ecx
> movl %ecx, BP_code32_start(%eax)
>
> sub $0x4, %esp
Woa, nice catch!
The commit message could do with a little work however. In particular
the usual way to refer to a commit is like this: commit 35d5134b7d5a
("x86/efi: Correct EFI boot stub use of code32_start"). And the
Signed-off-by line should contain your full name.
Luis, Greg, what is the procedure for submitting a patch that is only
required for stable?
--
Matt Fleming, Intel Open Source Technology Center
next parent reply other threads:[~2015-07-30 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438078879-24705-1-git-send-email-fupan.li@windriver.com>
2015-07-30 15:04 ` Matt Fleming [this message]
2015-07-30 16:31 ` [PATCH 3.10 ~ 3.14] efi: fix the efi 32bit boot failed problem Greg KH
[not found] ` <20150730163102.GA19943-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-07-30 16:45 ` Matt Fleming
2015-07-30 16:59 ` Greg KH
[not found] ` <20150730165943.GD5515-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2015-07-31 1:22 ` fupan
2015-07-31 12:05 ` Matt Fleming
2015-07-31 12:21 ` Luis Henriques
2015-08-03 1:38 ` fupan
2015-08-03 2:12 ` fupan
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=20150730150428.GJ2725@codeblueprint.co.uk \
--to=matt@codeblueprint.co.uk \
--cc=fupan.li@windriver.com \
--cc=fupanli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.henriques@canonical.com \
--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).