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/misc updates for v6.4-rc1
Date: Mon, 24 Apr 2023 16:00:29 +0200 [thread overview]
Message-ID: <20230424140029.GEZEaLfYPda4W38IHj@fat_crate.local> (raw)
Hi Linus,
please pull the pile of miscellaneous x86 updates for 6.4.
Thx.
---
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_misc_for_v6.4_rc1
for you to fetch changes up to 5910f06503aae3cc4890e562683abc3e38857ff9:
MAINTAINERS: Add x86 hardware vulnerabilities section (2023-03-10 11:13:30 +0100)
----------------------------------------------------------------
- Add a x86 hw vulnerabilities section to MAINTAINERS so that the folks
involved in it can get CCed on patches
- Add some more CPUID leafs to the kcpuid tool and extend its
functionality to be more useful when grepping for CPUID bits
----------------------------------------------------------------
Borislav Petkov (AMD) (1):
tools/x86/kcpuid: Dump the CPUID function in detailed view
Josh Poimboeuf (1):
MAINTAINERS: Add x86 hardware vulnerabilities section
Terry Bowman (2):
tools/x86/kcpuid: Fix avx512bw and avx512lvl fields in Fn00000007
tools/x86/kcpuid: Update AMD leaf Fn80000001
MAINTAINERS | 11 ++++++++
tools/arch/x86/kcpuid/cpuid.csv | 61 +++++++++++++++++++++++++++++++++++++----
tools/arch/x86/kcpuid/kcpuid.c | 32 ++++++++++++++++-----
3 files changed, 92 insertions(+), 12 deletions(-)
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next reply other threads:[~2023-04-24 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 14:00 Borislav Petkov [this message]
2023-04-25 18:00 ` 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=20230424140029.GEZEaLfYPda4W38IHj@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
all inboxes | Powered by JetHome®