From: Sohil Mehta <sohil.mehta@intel.com>
To: Dave Hansen <dave.hansen@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: Tue, 3 Feb 2026 11:09:34 -0800 [thread overview]
Message-ID: <5e5208fb-d1af-43a5-86de-e009901e272f@intel.com> (raw)
In-Reply-To: <5e3dc792-c5aa-4024-b2a3-32db49da8132@intel.com>
On 2/2/2026 10:01 AM, Dave Hansen wrote:
>> 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.
Great, I think we can avoid the find duplicates logic in that case.
next prev parent reply other threads:[~2026-02-03 19:09 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
2026-02-03 19:09 ` Sohil Mehta [this message]
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=5e5208fb-d1af-43a5-86de-e009901e272f@intel.com \
--to=sohil.mehta@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--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=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