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] EFI fixes for v6.6 (#2)
Date: Fri, 22 Sep 2023 09:40:27 +0000	[thread overview]
Message-ID: <20230922094027.204834-1-ardb@kernel.org> (raw)

Hello Linus,

Please pull this follow-up fix for the unaccepted memory fix merged last week
as part of the first EFI fixes batch. The unaccepted memory table needs to be
accessible very early, even in cases (such as crashkernels) where the direct
map does not cover all of DRAM, and so it is added to memblock explicitly, and
subsequently memblock_reserve()'d as before.

The following changes since commit 79b83606abc778aa3cbee535b362ce905d0b9448:

  efivarfs: fix statfs() on efivarfs (2023-09-11 09:10:02 +0000)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-fixes-for-v6.6-2

for you to fetch changes up to 8dbe33956d96c9d066ef15ca933ede30748198b2:

  efi/unaccepted: Make sure unaccepted table is mapped (2023-09-19 16:11:36 +0000)

----------------------------------------------------------------
EFI fixes for v6.6 take 2:

- fix boot regression on SEV-SNP (and TDX) caused by a fix in the
  preceding batch

----------------------------------------------------------------
Kirill A. Shutemov (1):
      efi/unaccepted: Make sure unaccepted table is mapped

 drivers/firmware/efi/efi.c | 32 +++++++++++++++++++++++++++++---
 1 file changed, 29 insertions(+), 3 deletions(-)

             reply	other threads:[~2023-09-22  9:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  9:40 Ard Biesheuvel [this message]
2023-09-22 16:43 ` [GIT PULL] EFI fixes for v6.6 (#2) 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=20230922094027.204834-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