From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
x86@kernel.org, Borislav Petkov <bp@suse.de>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: Re: [PATCH stable] x86/microcode: do not cache microcode if it will not be used
Date: Wed, 17 Jan 2024 12:00:29 +0100 [thread overview]
Message-ID: <2024011756-dosage-deviator-6e03@gregkh> (raw)
In-Reply-To: <2024011543-dropout-alienable-a9e9@gregkh>
On Mon, Jan 15, 2024 at 09:59:23PM +0100, Greg KH wrote:
> On Mon, Jan 15, 2024 at 07:54:59PM +0100, Paolo Bonzini wrote:
> > On Mon, Jan 15, 2024 at 7:35 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> > >
> > > On Mon, Jan 15, 2024 at 11:22:02AM +0100, Paolo Bonzini wrote:
> > > > [ Upstream commit a7939f01672034a58ad3fdbce69bb6c665ce0024 ]
> > >
> > > This really isn't this commit id, sorry.
> >
> > True, that's the point of the mainline kernel where the logic most
> > closely resembles the patch. stable-kernel-rules.rst does not quite
> > say what to do in this case.
>
> Ok, then just say, "this is not upstream" and the rest of your changelog
> is good. I'll edit it up tomorrow and apply it, thanks.
Ok, now queued up for 6.6.y, but what about older kernel versions? Is
this relevant for them as well? I will note that it does seem to apply
to them properly and build, is it not relevant?
thanks,
greg k-h
next prev parent reply other threads:[~2024-01-17 11:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 10:22 [PATCH stable] x86/microcode: do not cache microcode if it will not be used Paolo Bonzini
2024-01-15 10:56 ` Borislav Petkov
2024-01-15 18:35 ` Greg KH
2024-01-15 18:54 ` Paolo Bonzini
2024-01-15 20:59 ` Greg KH
2024-01-17 11:00 ` Greg KH [this message]
2024-01-17 11:57 ` Paolo Bonzini
2024-01-17 12:08 ` 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=2024011756-dosage-deviator-6e03@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stable@vger.kernel.org \
--cc=x86@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).