From: Greg KH <gregkh@linuxfoundation.org>
To: Borislav Petkov <bp@suse.de>
Cc: ssengar@linux.microsoft.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] x86/cacheinfo: Add a cpu_llc_shared_mask() UP variant" failed to apply to 5.15-stable tree
Date: Wed, 5 Oct 2022 13:05:47 +0200 [thread overview]
Message-ID: <Yz1lC0ol1lhhnIn+@kroah.com> (raw)
In-Reply-To: <Yz1gP2FLEbjLIL9y@zn.tnic>
On Wed, Oct 05, 2022 at 12:45:19PM +0200, Borislav Petkov wrote:
> On Mon, Oct 03, 2022 at 08:20:27AM +0200, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.15-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > Possible dependencies:
> >
> > df5b035b5683 ("x86/cacheinfo: Add a cpu_llc_shared_mask() UP variant")
> > 66558b730f25 ("sched: Add cluster scheduler level for x86")
>
> This is a fix for CONFIG_SMP=n kernels which was caught by testing this
> explicitly by disabling SMP. IOW, I don't think anyone would be running
> SMP=n kernels and thus maybe should not backport those...?
Yeah, I agree, this doesn't look like a valid thing to backport, if
people had this issue in 5.15.y they would have already reported by now.
thanks,
greg k-h
prev parent reply other threads:[~2022-10-05 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 6:20 FAILED: patch "[PATCH] x86/cacheinfo: Add a cpu_llc_shared_mask() UP variant" failed to apply to 5.15-stable tree gregkh
2022-10-05 10:45 ` Borislav Petkov
2022-10-05 11:05 ` 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=Yz1lC0ol1lhhnIn+@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=ssengar@linux.microsoft.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