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/urgent for v6.9
Date: Sun, 12 May 2024 09:38:21 +0200 [thread overview]
Message-ID: <20240512073821.GAZkBx7VXlioXx6q6w@fat_crate.local> (raw)
Hi Linus,
please pull the last two x86 urgent fixes for v6.9.
The merge window lineup is tested, pretty much all outstanding
regressions I know of are addressed, I think we're ready as we can ever
be...
:-)
Thx.
---
The following changes since commit dd5a440a31fae6e459c0d6271dddd62825505361:
Linux 6.9-rc7 (2024-05-05 14:06:01 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip tags/x86_urgent_for_v6.9
for you to fetch changes up to 5754ace3c3199c162dcee1f3f87a538c46d1c832:
x86/topology/amd: Ensure that LLC ID is initialized (2024-05-10 17:42:50 +0200)
----------------------------------------------------------------
- Add a new PCI ID which belongs to a new AMD CPU family 0x1a
- Ensure that that last level cache ID is set in all cases, in the AMD
CPU topology parsing code, in order to prevent invalid scheduling
domain CPU masks
----------------------------------------------------------------
Shyam Sundar S K (1):
x86/amd_nb: Add new PCI IDs for AMD family 0x1a
Thomas Gleixner (1):
x86/topology/amd: Ensure that LLC ID is initialized
arch/x86/kernel/amd_nb.c | 1 +
arch/x86/kernel/cpu/topology_amd.c | 16 +++++++---------
include/linux/pci_ids.h | 1 +
3 files changed, 9 insertions(+), 9 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2024-05-12 7:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 7:38 Borislav Petkov [this message]
2024-05-12 16:11 ` [GIT PULL] x86/urgent for v6.9 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=20240512073821.GAZkBx7VXlioXx6q6w@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;
as well as URLs for NNTP newsgroup(s).