From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi <linux-efi@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] EFI fixes for v5.9
Date: Sun, 11 Oct 2020 20:52:41 +0200 [thread overview]
Message-ID: <CAMj1kXHuSThL1aYUC3E7uAGhOJ3g5=5O9Qmw9p6XqXq0UsyHhA@mail.gmail.com> (raw)
In-Reply-To: <20200929182412.31858-1-ardb@kernel.org>
On Tue, 29 Sep 2020 at 20:24, Ard Biesheuvel <ardb@kernel.org> 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@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Borislav Petkov <bp@alien8.de>
>
> ----------------------------------------------------------------
> 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(-)
prev parent reply other threads:[~2020-10-11 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 18:24 [GIT PULL] EFI fixes for v5.9 Ard Biesheuvel
2020-10-11 18:52 ` Ard Biesheuvel [this message]
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='CAMj1kXHuSThL1aYUC3E7uAGhOJ3g5=5O9Qmw9p6XqXq0UsyHhA@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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).