All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>
Subject: Re: [GIT PULL] EFI fixes for v5.14-rc2
Date: Tue, 20 Jul 2021 13:33:50 +0200	[thread overview]
Message-ID: <YPa0nvuYa5apyQTV@gmail.com> (raw)
In-Reply-To: <20210720073311.55452-1-ardb@kernel.org>


* Ard Biesheuvel <ardb@kernel.org> wrote:

> The following changes since commit e73f0f0ee7541171d89f2e2491130c7771ba58d3:
> 
>   Linux 5.14-rc1 (2021-07-11 15:07:40 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-urgent-for-v5.14-rc2
> 
> for you to fetch changes up to 47e1e233e9d822dfda068383fb9a616451bda703:
> 
>   efi/mokvar: Reserve the table only if it is in boot services data (2021-07-20 09:28:09 +0200)
> 
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Borislav Petkov <bp@alien8.de>
> 
> ----------------------------------------------------------------
> EFI fixes for v5.14-rc2:
> 
> - Ensure that memblock reservations and IO reserved resources remain in
> sync when using the EFI memreserve feature.
> - Don't complain about invalid TPM final event log table if it is
> missing altogether.
> - Comment header fix for the stub.
> - Avoid a spurious warning when attempting to reserve firmware memory
> that is already reserved in the first place.

>  4 files changed, 23 insertions(+), 7 deletions(-)

Pulled into tip:efi/urgent, thanks a lot Ard!

	Ingo

      reply	other threads:[~2021-07-20 11:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-20  7:33 [GIT PULL] EFI fixes for v5.14-rc2 Ard Biesheuvel
2021-07-20 11:33 ` Ingo Molnar [this message]

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=YPa0nvuYa5apyQTV@gmail.com \
    --to=mingo@kernel.org \
    --cc=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=linux-efi@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.