From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Cc: "Borislav Petkov (AMD)" <bp@alien8.de>, stable@vger.kernel.org
Subject: Re: Request to port to 6.6.y : c809b0d0e52d ("x86/microcode/AMD: Flush patch buffer mapping after application")
Date: Mon, 23 Dec 2024 16:49:23 +0100 [thread overview]
Message-ID: <2024122346-dispersal-stream-f472@gregkh> (raw)
In-Reply-To: <Z2lkZC_MgXe4rDRW@antipodes>
On Mon, Dec 23, 2024 at 02:23:48PM +0100, Thomas De Schampheleire wrote:
> I cannot currently move to 6.12 for these systems, this has other consequences
> and testing efforts.
Why? Your testing efforts should be identical for a stable kernel
update or a movement to a new kernel version. What is not working
properly for you in 6.12.y?
thanks,
greg k-h
prev parent reply other threads:[~2024-12-23 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 15:32 Request to port to 6.6.y : c809b0d0e52d ("x86/microcode/AMD: Flush patch buffer mapping after application") Thomas De Schampheleire
2024-12-17 15:53 ` Greg KH
2024-12-18 12:28 ` Thomas De Schampheleire
2024-12-23 12:33 ` Greg KH
2024-12-23 13:23 ` Thomas De Schampheleire
2024-12-23 15:49 ` 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=2024122346-dispersal-stream-f472@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bp@alien8.de \
--cc=stable@vger.kernel.org \
--cc=thomas.de_schampheleire@nokia.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.