From: Greg KH <gregkh@linuxfoundation.org>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: ailin.xu@intel.com, bp@suse.de, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/cpu: Add Xeon Icelake-D to list of CPUs that support PPIN" failed to apply to 5.10-stable tree
Date: Mon, 31 Jan 2022 18:35:54 +0100 [thread overview]
Message-ID: <Yfgd+nHcTbNcSHY0@kroah.com> (raw)
In-Reply-To: <YfgZaKupZpQobmiA@agluck-desk2.amr.corp.intel.com>
On Mon, Jan 31, 2022 at 09:16:24AM -0800, Luck, Tony wrote:
> >From 72a73811c4bd53e0ec8284c12180068468d7c733 Mon Sep 17 00:00:00 2001
> From: Tony Luck <tony.luck@intel.com>
> Date: Mon, 31 Jan 2022 09:00:41 -0800
> Subject: [PATCH] x86/cpu: Add Sapphire Rapids and Icelake-D to list of CPUs that support PPIN
>
> commit a331f5fdd36dba1ffb0239a4dfaaf1df91ff1aab upstream
> commit e464121f2d40eabc7d11823fb26db807ce945df4 upstream
>
> Add Sapphire Rapids and Icelake-D to list of CPUs that support PPIN
>
> Signed-off-by: Tony Luck <tony.luck@intel.com>
> ---
>
> Failed to backport because the sapphire rapids CPU model number
> patch had not been backported. Bundled both together here. But if
> that breaks stable rules or scripts, I can redo as two patches one
> for each upstream commit.
Two patches please.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-31 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 12:34 FAILED: patch "[PATCH] x86/cpu: Add Xeon Icelake-D to list of CPUs that support PPIN" failed to apply to 5.10-stable tree gregkh
2022-01-31 17:16 ` Luck, Tony
2022-01-31 17:35 ` Greg KH [this message]
2022-01-31 17:43 ` [v5.10 stable PATCH 1/2] x86/mce: Add Xeon Sapphire Rapids to list of CPUs that support PPIN Tony Luck
2022-01-31 17:43 ` [v5.10 stable PATCH 2/2] x86/cpu: Add Xeon Icelake-D " Tony Luck
2022-02-03 18:01 ` Greg Kroah-Hartman
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=Yfgd+nHcTbNcSHY0@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ailin.xu@intel.com \
--cc=bp@suse.de \
--cc=stable@vger.kernel.org \
--cc=tony.luck@intel.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 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.