From: Ard Biesheuvel <ardb+git@google.com>
To: torvalds@linux-foundation.org
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] EFI updates for v6.19
Date: Tue, 2 Dec 2025 10:52:00 +0100 [thread overview]
Message-ID: <20251202095159.1183189-2-ardb+git@google.com> (raw)
From: Ard Biesheuvel <ardb@kernel.org>
Hi Linus,
The usual trickle of EFI contributions. There are some arm64 specific change
this cycle too, but they will land via the arm64 tree.
Please pull.
The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
Linux 6.18-rc1 (2025-10-12 13:42:36 -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.19
for you to fetch changes up to 7a2ff00c3b5e3ca1bbeb13cda52efe870be8501b:
docs: efi: add CPER functions to driver-api (2025-11-21 09:42:03 +0100)
----------------------------------------------------------------
EFI updates for v6.19:
- Parse SMBIOS tables in memory directly on Macbooks that do not
implement the EFI SMBIOS protocol
- Obtain EDID information from the primary display while running in the
EFI stub, and expose it via bootparams on x86 (generic method is in
the works, and will likely land during the next cycle)
- Bring CPER handling for ARM systems up to data with the latest EFI
spec changes.
- Various cosmetic changes.
----------------------------------------------------------------
Breno Leitao (1):
efi/memattr: Convert efi_memattr_init() return type to void
Francesco Pompo (1):
efistub/x86: Add fallback for SMBIOS record lookup
Jason Tian (1):
RAS: Report all ARM processor CPER information to userspace
Mauro Carvalho Chehab (4):
efi/cper: Adjust infopfx size to accept an extra space
efi/cper: Add a new helper function to print bitmasks
efi/cper: align ARM CPER type with UEFI 2.9A/2.10 specs
docs: efi: add CPER functions to driver-api
Qiang Ma (1):
efi/riscv: Remove the useless failure return message print
Randy Dunlap (1):
efi: stmm: fix kernel-doc "bad line" warnings
Thomas Zimmermann (5):
efi: Fix trailing whitespace in header file
efi/libstub: gop: Find GOP handle instead of GOP data
efi/libstub: gop: Initialize screen_info in helper function
efi/libstub: gop: Add support for reading EDID
efi/libstub: x86: Store EDID in boot_params
Documentation/driver-api/firmware/efi/index.rst | 11 +-
drivers/acpi/apei/ghes.c | 27 ++---
drivers/firmware/efi/cper-arm.c | 52 +++++----
drivers/firmware/efi/cper.c | 62 ++++++++++-
drivers/firmware/efi/libstub/efi-stub.c | 2 +-
drivers/firmware/efi/libstub/efistub.h | 31 +++++-
drivers/firmware/efi/libstub/gop.c | 137 +++++++++++++++---------
drivers/firmware/efi/libstub/x86-stub.c | 104 +++++++++++++++++-
drivers/firmware/efi/memattr.c | 7 +-
drivers/firmware/efi/riscv-runtime.c | 10 +-
drivers/firmware/efi/stmm/mm_communication.h | 6 +-
drivers/ras/ras.c | 40 ++++++-
include/linux/cper.h | 12 ++-
include/linux/efi.h | 6 +-
include/linux/ras.h | 16 ++-
include/ras/ras_event.h | 49 ++++++++-
16 files changed, 438 insertions(+), 134 deletions(-)
next reply other threads:[~2025-12-02 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 9:52 Ard Biesheuvel [this message]
2025-12-05 1:53 ` [GIT PULL] EFI updates for v6.19 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=20251202095159.1183189-2-ardb+git@google.com \
--to=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=torvalds@linux-foundation.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