From: Dave Hansen <dave.hansen@intel.com>
To: Sohil Mehta <sohil.mehta@intel.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Cc: Thomas Gleixner <tglx@kernel.org>, 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>,
linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
x86@kernel.org
Subject: Re: [PATCH v4] scripts/x86/intel: Add a script to update the old microcode list
Date: Mon, 2 Feb 2026 10:01:10 -0800 [thread overview]
Message-ID: <5e3dc792-c5aa-4024-b2a3-32db49da8132@intel.com> (raw)
In-Reply-To: <d0835c59-7989-4d41-b63f-82f7da0e6fab@intel.com>
On 1/30/26 15:09, Sohil Mehta wrote:
> Dave probably has a use case where he passes multiple directories to the
> script. IIUC, the new version just inserts a unique entry for every FMS
> + pf_mask and skips the repeats. But it doesn't necessarily use the
> latest revision for the duplicates. We probably need an equivalent logic
> for this:
>
> if existing is not None:
> # If the existing one is newer, just move on:
> if existing['rev'] > rev['rev']:
> continue
>
> Dave, opinion?
I can't think of a case where I wanted to use multiple directories for a
single run of the script. The only thing I tend to do is switch between
the distr-provided ucode in /lib/firmware and a local clone of the Intel
microcode git repo. So, one or the other, not both at once.
next prev parent reply other threads:[~2026-02-02 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 19:47 [PATCH v4] scripts/x86/intel: Add a script to update the old microcode list Sohil Mehta
2026-01-30 22:00 ` Andrew Cooper
2026-01-30 23:09 ` Sohil Mehta
2026-02-02 18:01 ` Dave Hansen [this message]
2026-02-03 19:09 ` Sohil Mehta
2026-02-10 18:54 ` Luck, Tony
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=5e3dc792-c5aa-4024-b2a3-32db49da8132@intel.com \
--to=dave.hansen@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--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@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