From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/microcode for 7.4-rc1
Date: Mon, 19 Oct 2026 08:16:34 -0700 [thread overview]
Message-ID: <20261019151634.1857472-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull a x86/microcode change for 7.4-rc1. This one simply brings
the "old microcode" list up to the May 2026 release. This continues
the policy of intentionally lagging Intel's releases by roughly six
months, so when the kernel complains, it it for _really_ old
microcode.
--
The following changes since commit 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e:
Linux 7.3-rc5 (2026-09-27 13:55:01 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_microcode_for_7.4-rc1
for you to fetch changes up to cf086537af4e3b04f6012dae3766a51ed1afc61c:
x86/microcode/intel: Refresh old_microcode defines with the May 2026 release (2026-09-28 15:39:05 -0700)
----------------------------------------------------------------
- Refresh old_microcode defines with the May 2026 release
----------------------------------------------------------------
Sohil Mehta (1):
x86/microcode/intel: Refresh old_microcode defines with the May 2026 release
arch/x86/kernel/cpu/microcode/intel-ucode-defs.h | 91 ++++++++++++------------
1 file changed, 47 insertions(+), 44 deletions(-)
next reply other threads:[~2026-10-19 15:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 15:16 Dave Hansen [this message]
2026-10-20 22:37 ` [GIT PULL] x86/microcode for 7.4-rc1 pr-tracker-bot
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=20261019151634.1857472-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.