From: Ard Biesheuvel <ardb+git@google.com>
To: torvalds@google.com
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] EFI updates for v6.17
Date: Fri, 8 Aug 2025 23:46:07 -0700 [thread overview]
Message-ID: <20250809064606.35568-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
Apologies for the late notice - I was on vacation and wasn't aware of your
condensed schedule until today.
Please consider pulling the changes below.
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next-for-v6.17
for you to fetch changes up to 02eb7a8eee20b9ec6aafd5e17c5c41b53e8b13ef:
efi: add API doc entry for ovmf_debug_log (2025-07-15 04:15:30 +0200)
----------------------------------------------------------------
EFI updates for v6.17
- Expose the OVMF firmware debug log via sysfs
- Lower the default log level for the EFI stub to avoid corrupting any
splash screens with unimportant diagnostic output
----------------------------------------------------------------
Aaron Kling (1):
efistub: Lower default log level
Gerd Hoffmann (2):
efi: add ovmf debug log driver
efi: add API doc entry for ovmf_debug_log
Documentation/ABI/testing/sysfs-firmware-efi | 7 ++
drivers/firmware/efi/Kconfig | 8 ++
drivers/firmware/efi/Makefile | 1 +
drivers/firmware/efi/efi.c | 8 ++
drivers/firmware/efi/libstub/printk.c | 4 +-
drivers/firmware/efi/ovmf-debug-log.c | 111 +++++++++++++++++++++++++++
include/linux/efi.h | 4 +
7 files changed, 141 insertions(+), 2 deletions(-)
create mode 100644 drivers/firmware/efi/ovmf-debug-log.c
next reply other threads:[~2025-08-09 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 6:46 Ard Biesheuvel [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-09 7:52 [GIT PULL] EFI updates for v6.17 Ard Biesheuvel
2025-08-09 15:20 ` 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=20250809064606.35568-2-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=torvalds@google.com \
/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).