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: Build our own page table structures
Date: Fri, 1 Dec 2017 17:02:51 +0000 [thread overview]
Message-ID: <20171201170251.GA27374@kroah.com> (raw)
In-Reply-To: <BN6PR1201MB01310FA462AAF71126B84AD6F8390@BN6PR1201MB0131.namprd12.prod.outlook.com>
On Fri, Dec 01, 2017 at 04:27:09PM +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: Build our own page table structures
> >
> > On Fri, Dec 01, 2017 at 08:49:23AM +0000, Ghannam, Yazen wrote:
> > > Upstream commit ID: 67a9108ed4313b85a9c53406d80dc1ae3f8c3e36
> > > Prerequisite commit: "edc3b9129cec x86/mm/pat: Ensure cpa->pfn only
> > contains page frame numbers"
> > > Prerequisite commit: "c9f2a9a65e48 x86/efi: Hoist page table switching
> > code into efi_call_virt()"
> >
> > Again, you want all 3 of these patches applied to 4.4-stable? In what
> > order?
> >
>
> Yes please, in this order.
>
> 1) edc3b9129cecd0f0857112136f5b8b1bc1d45918
> 2) c9f2a9a65e4855b74d92cdad688f6ee4a1a323ff
> 3) 67a9108ed4313b85a9c53406d80dc1ae3f8c3e36
Now all applied.
greg k-h
prev parent reply other threads:[~2017-12-01 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 8:49 [PATCH] x86/efi: Build our own page table structures Ghannam, Yazen
2017-12-01 16:16 ` Greg KH
2017-12-01 16:27 ` Ghannam, Yazen
2017-12-01 17:02 ` Greg KH [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=20171201170251.GA27374@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 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).