On Tue, 29 Sep 2020 at 20:24, Ard Biesheuvel <ardb@xxxxxxxxxx> wrote: > > The following changes since commit 46908326c6b801201f1e46f5ed0db6e85bef74ae: > > efi: efibc: check for efivars write capability (2020-09-15 18:22:47 +0300) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v5.9-rc7 > > for you to fetch changes up to d32de9130f6c79533508e2c7879f18997bfbe2a0: > > efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure (2020-09-29 15:41:52 +0200) > > Cc: Ingo Molnar <mingo@xxxxxxxxxx> > Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx> > Cc: Borislav Petkov <bp@xxxxxxxxx> > > ---------------------------------------------------------------- > EFI fixes for v5.9: > - add definition of the EFI_MEMORY_CPU_CRYPTO memory attribute so we can > identify it in the memory map listings > - don't abort the boot on arm64 if the EFI RNG protocol is available but > returns with an error > - replace slashes with exclamation marks in efivarfs file names > - a couple of cosmetic fixups > > ---------------------------------------------------------------- > Ard Biesheuvel (2): > efi: Add definition of EFI_MEMORY_CPU_CRYPTO and ability to report it > efi/arm64: libstub: Deal gracefully with EFI_RNG_PROTOCOL failure > > Michael Schaller (1): > efivarfs: Replace invalid slashes with exclamation marks in dentries. > > Tian Tao (2): > efi/libstub: Fix missing-prototypes in string.c > efi: Delete deprecated parameter comments > What is the status of this PR? It went into tip afaict but it appears to be stuck there. > drivers/firmware/efi/efi.c | 47 ++++++++++++++++--------------- > drivers/firmware/efi/libstub/arm64-stub.c | 8 ++++-- > drivers/firmware/efi/libstub/fdt.c | 4 +-- > drivers/firmware/efi/libstub/string.c | 1 + > drivers/firmware/efi/vars.c | 1 - > fs/efivarfs/super.c | 3 ++ > include/linux/efi.h | 1 + > 7 files changed, 35 insertions(+), 30 deletions(-)
