From: Ard Biesheuvel <ardb@kernel.org>
To: linux-efi <linux-efi@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] EFI fixes for v5.8-rc
Date: Sat, 18 Jul 2020 08:54:20 +0300 [thread overview]
Message-ID: <CAMj1kXGHDS7PnuPsCnHWGDFdtcaJUuXboZUZQwowzw0LfrQ+pw@mail.gmail.com> (raw)
In-Reply-To: <20200709132807.32232-1-ardb@kernel.org>
On Thu, 9 Jul 2020 at 16:28, Ard Biesheuvel <ardb@kernel.org> wrote:
>
> The following changes since commit 2a55280a3675203496d302463b941834228b9875:
>
> efi/libstub: arm: Print CPU boot mode and MMU state at boot (2020-06-17 15:29:11 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v5.8-rc4
>
> for you to fetch changes up to 769e0fe1171e95d90ea5a2d6d0b2bdc7d5d2e7b2:
>
> efi: Revert "efi/x86: Fix build with gcc 4" (2020-07-09 10:14:29 +0300)
>
> ----------------------------------------------------------------
> EFI fixes for v5.8-rc4:
> - Fix the layering violation in the use of the EFI runtime services
> availability mask in users of the 'efivars' abstraction
> - Revert build fix for GCC v4.8 which is no longer supported
> - Some fixes for build issues found by Atish while working on RISC-V support
> - Avoid --whole-archive when linking the stub on arm64
> - Some x86 EFI stub cleanups from Arvind
>
> ----------------------------------------------------------------
> Ard Biesheuvel (2):
> efi/efivars: Expose RT service availability via efivars abstraction
> efi: Revert "efi/x86: Fix build with gcc 4"
>
> Arvind Sankar (2):
> efi/x86: Remove unused variables
> efi/x86: Only copy upto the end of setup_header
>
> Atish Patra (2):
> efi/libstub: Fix gcc error around __umoddi3 for 32 bit builds
> efi/libstub: Move the function prototypes to header file
>
> Masahiro Yamada (1):
> efi/libstub/arm64: link stub lib.a conditionally
>
> arch/arm64/Makefile | 2 +-
> drivers/firmware/efi/efi-pstore.c | 5 +----
> drivers/firmware/efi/efi.c | 12 ++++++++----
> drivers/firmware/efi/efivars.c | 5 +----
> drivers/firmware/efi/libstub/Makefile | 3 +--
> drivers/firmware/efi/libstub/alignedmem.c | 2 +-
> drivers/firmware/efi/libstub/efi-stub.c | 17 -----------------
> drivers/firmware/efi/libstub/efistub.h | 16 ++++++++++++++++
> drivers/firmware/efi/libstub/x86-stub.c | 8 ++++----
> drivers/firmware/efi/vars.c | 6 ++++++
> fs/efivarfs/super.c | 6 +++---
> include/linux/efi.h | 1 +
> 12 files changed, 43 insertions(+), 40 deletions(-)
Ping?
next prev parent reply other threads:[~2020-07-18 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 13:28 [GIT PULL] EFI fixes for v5.8-rc Ard Biesheuvel
2020-07-18 5:54 ` Ard Biesheuvel [this message]
2020-07-21 5:28 ` Ard Biesheuvel
2020-07-25 10:25 ` Ingo Molnar
2020-07-25 12:12 ` 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=CAMj1kXGHDS7PnuPsCnHWGDFdtcaJUuXboZUZQwowzw0LfrQ+pw@mail.gmail.com \
--to=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).