From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-efi@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Jonathan Richardson <jonathan.richardson@broadcom.com>,
Luo XinanX <xinanx.luo@intel.com>,
"Prakhya, Sai Praneeth" <sai.praneeth.prakhya@intel.com>,
Qian Cai <cai@lca.pw>, Tian Baofeng <baofeng.tian@intel.com>
Subject: [GIT PULL 0/4] EFI fixes for v5.2
Date: Sat, 22 Jun 2019 10:51:02 +0200 [thread overview]
Message-ID: <20190622085106.24859-1-ard.biesheuvel@linaro.org> (raw)
The following changes since commit d1fdb6d8f6a4109a4263176c84b899076a5f8008:
Linux 5.2-rc4 (2019-06-08 20:24:46 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent
for you to fetch changes up to 975a6166a8584ee4a1b8bd93098e49dc101d7171:
efibc: Replace variable set function in notifier call (2019-06-22 10:24:57 +0200)
----------------------------------------------------------------
Another handful of EFI fixes for v5.2:
- fix a potential crash after kexec on arm64 with GICv3
- fix a build warning on x86
- stop policing the BGRT feature flags
- use a non-blocking version of SetVariable() in the boot control driver
----------------------------------------------------------------
Ard Biesheuvel (1):
efi/memreserve: deal with memreserve entries in unmapped memory
Hans de Goede (1):
efi/bgrt: Drop BGRT status field reserved bits check
Qian Cai (1):
x86/efi: fix a -Wtype-limits compilation warning
Tian Baofeng (1):
efibc: Replace variable set function in notifier call
arch/x86/platform/efi/quirks.c | 2 +-
drivers/firmware/efi/efi-bgrt.c | 5 -----
drivers/firmware/efi/efi.c | 12 ++++++++++--
drivers/firmware/efi/efibc.c | 12 +++++++-----
4 files changed, 18 insertions(+), 13 deletions(-)
next reply other threads:[~2019-06-22 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 8:51 Ard Biesheuvel [this message]
2019-06-22 8:51 ` [PATCH 1/4] efi/memreserve: deal with memreserve entries in unmapped memory Ard Biesheuvel
2019-06-22 8:51 ` [PATCH 2/4] efi/bgrt: Drop BGRT status field reserved bits check Ard Biesheuvel
2019-06-22 8:51 ` [PATCH 3/4] x86/efi: fix a -Wtype-limits compilation warning Ard Biesheuvel
2019-06-22 8:51 ` [PATCH 4/4] efibc: Replace variable set function in notifier call Ard Biesheuvel
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=20190622085106.24859-1-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=baofeng.tian@intel.com \
--cc=cai@lca.pw \
--cc=hdegoede@redhat.com \
--cc=jonathan.richardson@broadcom.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sai.praneeth.prakhya@intel.com \
--cc=tglx@linutronix.de \
--cc=xinanx.luo@intel.com \
/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).