stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: fupan <fupan.li@windriver.com>
To: Luis Henriques <luis.henriques@canonical.com>,
	Matt Fleming <matt@codeblueprint.co.uk>
Cc: Jiri Slaby <jslaby@suse.cz>, Greg KH <gregkh@linuxfoundation.org>,
	<linux-kernel@vger.kernel.org>, <fupanli@gmail.com>,
	<linux-efi@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 3.10 ~ 3.14] efi: fix the efi 32bit boot failed problem
Date: Mon, 3 Aug 2015 09:38:23 +0800	[thread overview]
Message-ID: <55BEC60F.1040404@windriver.com> (raw)
In-Reply-To: <20150731122150.GB2626@ares>

On 07/31/2015 08:21 PM, Luis Henriques wrote:
> On Fri, Jul 31, 2015 at 01:05:19PM +0100, Matt Fleming wrote:
>> On Fri, 31 Jul, at 09:22:33AM, fupan wrote:
>>> Hi, Matt
>>>
>>> Will you take care of this patch or I send a V2?
>>   
>> Could you please send a V2 with the changes to the commit message that I
>> suggested previously? Thanks!
>>
> I'm replying to this thread simply to include Jiri on the CC list as I
> believe 3.12 will also require this fix.  Please make sure he's in the
> list for the v2.
Hi, Lu�s

No problem.

BTW, actually all of the branch from 3.10 to 3.14 will need this fix.

Fupan
>
> [ It looks like the 3.16 kernel I'm maintaining isn't affected, BTW. ]
>
> Cheers,
> --
> Lu�s
>
>


  reply	other threads:[~2015-08-03  1:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28 10:21 [PATCH 3.10 ~ 3.14] efi: fix the efi 32bit boot failed problem fupan.li
2015-07-28 15:15 ` Greg KH
2015-07-30 15:04 ` Matt Fleming
2015-07-30 16:31   ` Greg KH
2015-07-30 16:45     ` Matt Fleming
2015-07-30 16:59       ` Greg KH
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 [this message]
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=55BEC60F.1040404@windriver.com \
    --to=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=luis.henriques@canonical.com \
    --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;
as well as URLs for NNTP newsgroup(s).