From: Ben Hutchings <ben@decadent.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>, fupan.li@windriver.com
Cc: matt@codeblueprint.co.uk, jslaby@suse.cz,
linux-efi@vger.kernel.org, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, fupanli@gmail.com
Subject: Re: [PATCH V2] efi: fix 32bit kernel boot failed problem using efi
Date: Mon, 03 Aug 2015 23:15:33 +0100 [thread overview]
Message-ID: <1438640133.3225.112.camel@decadent.org.uk> (raw)
In-Reply-To: <20150803161509.GA18377@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
On Mon, 2015-08-03 at 09:15 -0700, Greg KH wrote:
> On Mon, Aug 03, 2015 at 10:02:49AM +0800, fupan.li@windriver.com wrot
> e:
> > From: fli <fupan.li@windriver.com>
>
> This needs to match the signed-off-by line, otherwise I can't take it
> :(
>
> Please fix up and resend.
>
> And what -stable tree is this for?
The bug was introduced in 35d5134b7d5a on the 3.10 branch, but the same
bug in the backport seems to have been introduced on the 3.14 branch
and two others you don't maintain:
v3.10.39: 35d5134b7d5a x86/efi: Correct EFI boot stub use of code32_start
v3.12.20: 065487a10a22 x86/efi: Correct EFI boot stub use of code32_start
v3.14.3: 45ada9fae6d8 x86/efi: Correct EFI boot stub use of code32_start
v3.11.10.11: f32e88d764e3 x86/efi: Correct EFI boot stub use of code32_start
Ben.
--
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
prev parent reply other threads:[~2015-08-03 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 2:02 fupan.li
2015-08-03 11:39 ` Matt Fleming
2015-08-03 16:15 ` Greg KH
2015-08-03 22:15 ` Ben Hutchings [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=1438640133.3225.112.camel@decadent.org.uk \
--to=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=matt@codeblueprint.co.uk \
--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
Powered by JetHome