From: Greg KH <gregkh@linuxfoundation.org>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] x86/efi-bgrt: Replace early_memremap() with memremap()
Date: Sat, 2 Dec 2017 08:15:05 +0000 [thread overview]
Message-ID: <20171202081505.GC9978@kroah.com> (raw)
In-Reply-To: <BN6PR1201MB0131CCA9A753FDBCCE5728B3F8390@BN6PR1201MB0131.namprd12.prod.outlook.com>
On Fri, Dec 01, 2017 at 04:25:44PM +0000, Ghannam, Yazen wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Friday, December 1, 2017 11:16 AM
> > To: Ghannam, Yazen <Yazen.Ghannam@amd.com>
> > Cc: stable@vger.kernel.org
> > Subject: Re: [PATCH] x86/efi-bgrt: Replace early_memremap() with
> > memremap()
> >
> > On Fri, Dec 01, 2017 at 08:35:52AM +0000, Ghannam, Yazen wrote:
> > > Upstream commit ID: e2c90dd7e11e3025b46719a79fb4bb1e7a5cef9f
> > > Prerequisite commit: "50a0cb565246 x86/efi-bgrt: Fix kernel panic when
> > mapping BGRT data"
> >
> > So apply both of these patches to 4.4? Please be specific as I'm
> > confused here.
> >
>
> Yes, both.
>
> The first commit is the fix, and the second commit is needed for the first to
> apply cleanly.
>
> So cherry-pick
> 1) 50a0cb565246f20d59cdb161778531e4b19d35ac
> 2) e2c90dd7e11e3025b46719a79fb4bb1e7a5cef9f
>
> Sorry, I wasn't sure of the best way to describe this.
Both now applied, thanks.
greg k-h
next prev parent reply other threads:[~2017-12-02 8:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 8:35 [PATCH] x86/efi-bgrt: Replace early_memremap() with memremap() Ghannam, Yazen
2017-12-01 16:15 ` Greg KH
2017-12-01 16:25 ` Ghannam, Yazen
2017-12-02 8:15 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-21 14:12 Matt Fleming
2015-12-21 14:12 ` Matt Fleming
[not found] ` <1450707172-12561-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-21 20:07 ` Josh Triplett
2015-12-21 20:07 ` Josh Triplett
2016-01-04 13:12 ` Matt Fleming
2016-01-04 13:12 ` Matt Fleming
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=20171202081505.GC9978@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Yazen.Ghannam@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.