[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d677e21-a5a7-4b68-b11c-e73473bab0a6@intel.com>
Date: Fri, 22 Aug 2025 12:16:59 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Borislav Petkov <bp@...en8.de>
Cc: Sohil Mehta <sohil.mehta@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H . Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
Josh Poimboeuf <jpoimboe@...nel.org>,
Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>,
Nikolay Borisov <nik.borisov@...e.com>,
Andrew Cooper <andrew.cooper3@...rix.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] scripts/x86/intel: Add a script to update the minimum
ucode revisions
On 8/22/25 12:06, Borislav Petkov wrote:
> So as long as it unmistakenly specifies who updates the header, the script can
> be anywhere.
>
> I hope I'm making more sense.
Ahh, gotcha. Should we slap something like this in the script?
This script is intended to be run in response to releases of the
official Intel microcode github repository[link]. Typically,
someone at Intel would see a new release, run this script,
refresh the intel-ucode-defs.h file and send a patch upstream to
update the mainline and stable versions.
Powered by blists - more mailing lists