public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-efi@vger.kernel.org, keescook@chromium.org,
	Ard Biesheuvel <ardb@kernel.org>
Subject: [GIT PULL 1/2] EFI updates for v5.20
Date: Mon,  1 Aug 2022 15:41:16 +0200	[thread overview]
Message-ID: <20220801134117.1605678-2-ardb@kernel.org> (raw)
In-Reply-To: <20220801134117.1605678-1-ardb@kernel.org>

The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:

  Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next-for-v5.20

for you to fetch changes up to e3435fff6ae03ca3ec1279299664f968478067e2:

  ACPI: Move PRM config option under the main ACPI config (2022-06-30 17:36:03 +0200)

----------------------------------------------------------------
EFI updates for v5.20

- Enable mirrored memory for arm64
- Fix up several abuses of the efivar API
- Refactor the efivar API in preparation for moving the 'business logic'
  part of it into efivarfs
- Enable ACPI PRM on arm64

----------------------------------------------------------------
Ard Biesheuvel (13):
      efi: avoid efivars layer when loading SSDTs from variables
      efi: efibc: avoid efivar API for setting variables
      media: atomisp_gmin_platform: stop abusing efivar API
      iwlwifi: Switch to proper EFI variable store interface
      brcmfmac: Switch to appropriate helper to load EFI variable contents
      selftests/kexec: remove broken EFI_VARS secure boot fallback check
      Input: applespi - avoid efivars API and invoke EFI services directly
      pstore: Add priv field to pstore_record for backend specific use
      efi: vars: Don't drop lock in the middle of efivar_init()
      efi: vars: Add thin wrapper around EFI get/set variable interface
      efi: pstore: Omit efivars caching EFI varstore access layer
      efi: vars: Use locking version to iterate over efivars linked lists
      efi: vars: Drop __efivar_entry_iter() helper which is no longer used

Liu Zixian (1):
      efi: Correct comment on efi_memmap_alloc

Ma Wupeng (5):
      efi: Make code to find mirrored memory ranges generic
      mm: Ratelimited mirrored memory related warning messages
      mm: Limit warning message in vmemmap_verify() to once
      arm64: mm: Only remove nomap flag for initrd
      memblock: Disable mirror feature if kernelcore is not specified

Sudeep Holla (4):
      efi: Simplify arch_efi_call_virt() macro
      ACPI: PRM: Change handler_addr type to void pointer
      ACPI: Enable Platform Runtime Mechanism(PRM) support on ARM64
      ACPI: Move PRM config option under the main ACPI config

Zheng Zhi Yuan (1):
      drivers: fix typo in firmware/efi/memmap.c

 arch/arm/include/asm/efi.h                         |   7 -
 arch/arm64/include/asm/efi.h                       |   7 +-
 arch/arm64/mm/init.c                               |   2 +-
 arch/loongarch/include/asm/efi.h                   |  16 +-
 arch/riscv/include/asm/efi.h                       |   2 -
 arch/x86/include/asm/efi.h                         |   7 +-
 arch/x86/platform/efi/efi.c                        |  23 --
 drivers/acpi/Kconfig                               |  30 +-
 drivers/acpi/prmt.c                                |   4 +-
 drivers/firmware/efi/Kconfig                       |   2 +
 drivers/firmware/efi/efi-init.c                    |   1 +
 drivers/firmware/efi/efi-pstore.c                  | 377 +++++----------------
 drivers/firmware/efi/efi.c                         | 126 +++----
 drivers/firmware/efi/efibc.c                       |  76 ++---
 drivers/firmware/efi/efivars.c                     |  25 +-
 drivers/firmware/efi/memmap.c                      |   5 +-
 drivers/firmware/efi/vars.c                        | 258 +++++++++-----
 drivers/input/keyboard/applespi.c                  |  42 +--
 .../broadcom/brcm80211/brcmfmac/firmware.c         |  25 +-
 drivers/net/wireless/intel/iwlwifi/fw/uefi.c       |  96 ++----
 .../media/atomisp/pci/atomisp_gmin_platform.c      |  27 +-
 fs/efivarfs/super.c                                |  15 +-
 fs/pstore/inode.c                                  |   1 +
 fs/pstore/platform.c                               |   1 +
 include/linux/efi.h                                |  33 +-
 include/linux/pstore.h                             |   4 +
 mm/internal.h                                      |   2 +
 mm/memblock.c                                      |   7 +-
 mm/page_alloc.c                                    |   2 +-
 mm/sparse-vmemmap.c                                |   2 +-
 tools/testing/selftests/kexec/kexec_common_lib.sh  |  36 +-
 31 files changed, 486 insertions(+), 775 deletions(-)

  reply	other threads:[~2022-08-01 13:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 13:41 [GIT PULL 0/2] EFI pull requests for v5.20 Ard Biesheuvel
2022-08-01 13:41 ` Ard Biesheuvel [this message]
2022-08-03 22:29   ` [GIT PULL 1/2] EFI updates " pr-tracker-bot
2022-08-01 13:41 ` [GIT PULL 2/2] EFI removal of efivars sysfs driver Ard Biesheuvel
2022-08-03 21:43   ` Linus Torvalds
2022-08-03 22:29   ` 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=20220801134117.1605678-2-ardb@kernel.org \
    --to=ardb@kernel.org \
    --cc=keescook@chromium.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