From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/boot changes for v7.3
Date: Mon, 17 Aug 2026 12:17:05 +0200 [thread overview]
Message-ID: <aoLfoSA7uUyGPyQu@gmail.com> (raw)
Linus,
Please pull the latest x86/boot Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-boot-2026-08-17
for you to fetch changes up to 2082fec6d4c65b4031dc82daa10cc9a5d35654c9:
x86/boot changes for v7.3:
- Misc simplifications and cleanups (Thorsten Blum)
Thanks,
Ingo
------------------>
Thorsten Blum (3):
x86/purgatory: Return bool from verify_sha256_digest()
x86/boot: Use IS_ENABLED() to simplify built-in-or-module checks
x86/boot: Use bool and IS_ENABLED() to simplify query_edd()
arch/x86/boot/edd.c | 20 ++++++++------------
arch/x86/boot/main.c | 10 ++++------
arch/x86/kernel/setup.c | 5 ++---
arch/x86/purgatory/purgatory.c | 14 ++++----------
4 files changed, 18 insertions(+), 31 deletions(-)
reply other threads:[~2026-08-17 10:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aoLfoSA7uUyGPyQu@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--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