Linux EFI development
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-efi@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL] More EFI fixes for v5.17
Date: Mon, 28 Feb 2022 10:12:56 +0100	[thread overview]
Message-ID: <20220228091256.814321-1-ardb@kernel.org> (raw)

The following changes since commit f5390cd0b43c2e54c7cf5506c7da4a37c5cef746:

  efi: runtime: avoid EFIv2 runtime services on Apple x86 machines (2022-01-23 10:31:27 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v5.17-2

for you to fetch changes up to 258dd902022cb10c83671176688074879517fd21:

  efivars: Respect "block" flag in efivar_entry_set_safe() (2022-02-28 10:07:50 +0100)

----------------------------------------------------------------
More EFI fixes for v5.17:

- don't treat valid hartid U32_MAX as a failure return code (RISC-V)
- avoid blocking query_variable_info() call when blocking is not allowed

----------------------------------------------------------------
Jann Horn (1):
      efivars: Respect "block" flag in efivar_entry_set_safe()

Sunil V L (1):
      riscv/efi_stub: Fix get_boot_hartid_from_fdt() return value

 drivers/firmware/efi/libstub/riscv-stub.c | 17 ++++++++++-------
 drivers/firmware/efi/vars.c               |  5 ++++-
 2 files changed, 14 insertions(+), 8 deletions(-)

             reply	other threads:[~2022-02-28  9:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  9:12 Ard Biesheuvel [this message]
2022-02-28 20:53 ` [GIT PULL] More EFI fixes for v5.17 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=20220228091256.814321-1-ardb@kernel.org \
    --to=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