The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/microcode for v7.0-rc1
Date: Tue, 10 Feb 2026 13:12:10 +0100	[thread overview]
Message-ID: <20260210121210.GAaYsgmpEhclwhenIW@fat_crate.local> (raw)

Hi Linus,

please pull a x86/microcode change for v7.0-rc1.

Thx.

---

The following changes since commit 9ace4753a5202b02191d54e9fdf7f9e3d02b85eb:

  Linux 6.19-rc4 (2026-01-04 14:41:55 -0800)

are available in the Git repository at:

  ssh://git@gitolite.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/x86_microcode_for_v7.0_rc1

for you to fetch changes up to ac44a110c18ad7bd9de0b809e861479ba97157d2:

  x86/microcode/AMD: Allow loader debugging to be enabled on baremetal too (2026-01-14 14:46:44 +0100)

----------------------------------------------------------------
- Since debugging the microcode loader makes sense on baremetal too (it was
  used in a guest only until now), extend it to be able to do that too.

----------------------------------------------------------------
Borislav Petkov (AMD) (1):
      x86/microcode/AMD: Allow loader debugging to be enabled on baremetal too

 arch/x86/Kconfig                         |  8 +++++---
 arch/x86/kernel/cpu/microcode/amd.c      |  4 ++--
 arch/x86/kernel/cpu/microcode/core.c     | 16 ++++++++++++----
 arch/x86/kernel/cpu/microcode/internal.h |  1 +
 4 files changed, 20 insertions(+), 9 deletions(-)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2026-02-10 12:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 12:12 Borislav Petkov [this message]
2026-02-11  3:28 ` [GIT PULL] x86/microcode for v7.0-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=20260210121210.GAaYsgmpEhclwhenIW@fat_crate.local \
    --to=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox