From: Ingo Molnar <mingo@kernel.org>
To: "Kani, Toshimitsu" <toshi.kani@hpe.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"eswierk@skyportsystems.com" <eswierk@skyportsystems.com>,
"paul.gortmaker@windriver.com" <paul.gortmaker@windriver.com>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: x86 PAT fixes for stable
Date: Wed, 25 May 2016 08:29:39 +0200 [thread overview]
Message-ID: <20160525062939.GB31368@gmail.com> (raw)
In-Reply-To: <1464111184.3504.60.camel@hpe.com>
* Kani, Toshimitsu <toshi.kani@hpe.com> wrote:
> Hello,
>
> The following patches fix two x86 PAT issues reported in 4.4 [1][2]. Can
> you please backport them up to 4.4?
Do they apply, build and boot cleanly in that order on top of v4.4, v4.5 and v4.6?
If yes then:
Acked-by: Ingo Molnar <mingo@kernel.org>
Thanks,
Ingo
next prev parent reply other threads:[~2016-05-25 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 17:42 x86 PAT fixes for stable Kani, Toshimitsu
2016-05-25 6:29 ` Ingo Molnar [this message]
2016-05-25 11:17 ` Ed Swierk
2016-05-25 15:20 ` Ed Swierk
2016-08-14 15:42 ` Greg KH
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=20160525062939.GB31368@gmail.com \
--to=mingo@kernel.org \
--cc=eswierk@skyportsystems.com \
--cc=paul.gortmaker@windriver.com \
--cc=stable@vger.kernel.org \
--cc=toshi.kani@hpe.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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).