From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Dave Hansen <dave.hansen@intel.com>, Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Sohil Mehta <sohil.mehta@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
X86-ML <x86@kernel.org>, KERNEL-ML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC] x86/microcode/intel: Refresh the revisions that determine old_microcode to 20250812 (Aug 2025)
Date: Sun, 5 Oct 2025 16:35:54 +0200 [thread overview]
Message-ID: <22502d77-81eb-4374-b8b8-d8a954daf859@gmail.com> (raw)
In-Reply-To: <8826a146-ba01-4f97-9fc5-7bf42c1e768d@intel.com>
On 10/5/25 5:58 AM, Dave Hansen wrote:
> Xose, do you have any specific, practical reasons this should be
> applied? Honestly, I don't hold the "HIGH" Intel SA rating in super high
> regard.
> In short, why do you care?
It does not seem relevant that the kernel displays obsolete information.
It's that simple.
prev parent reply other threads:[~2025-10-05 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 22:25 Xose Vazquez Perez
2025-10-05 2:42 ` Borislav Petkov
2025-10-05 3:58 ` Dave Hansen
2025-10-05 5:27 ` Borislav Petkov
2025-10-05 14:35 ` Xose Vazquez Perez [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=22502d77-81eb-4374-b8b8-d8a954daf859@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®