From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Arvind Sankar <nivedita@alum.mit.edu>
Subject: Re: [GIT PULL v2] EFI updates for v5.7
Date: Wed, 26 Feb 2020 15:27:14 +0100 [thread overview]
Message-ID: <20200226142713.GB3100@gmail.com> (raw)
In-Reply-To: <20200224133856.12832-1-ardb@kernel.org>
* Ard Biesheuvel <ardb@kernel.org> wrote:
> Hello Ingo, Thomas,
>
> I am sending this as an ordinary PR again, given the size. Please let me
> know if instead, you prefer me to send it out piecemeal as usual. Either
> works for me, I was just reluctant to spam people unsolicited.
>
> Note that EFI for RISC-V may still arrive this cycle as well.
>
> Please take special note of the GDT changes by Arvind. They were posted to
> the list without any feedback, and they look fine to me, but I know very
> little about these x86 CPU low level details.
>
> This was all build and boot tested on various different kinds of hardware,
> and all minor issues that were reported by the robots were fixed along the way.
>
> Please pull,
> Ard.
>
>
> The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:
>
> Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next
>
> for you to fetch changes up to dc235d62fc60a6549238eda7ff29769457fe5663:
>
> efi: Bump the Linux EFI stub major version number to #1 (2020-02-23 21:59:42 +0100)
> 66 files changed, 2718 insertions(+), 2638 deletions(-)
Pulled this as a Git tree, thanks Ard!
The boot-time GDT handling cleanups from Arvind look good to me too.
There's a couple of arguably scary commits in there, so these might be
'famous last words'. :-)
Thanks,
Ingo
next prev parent reply other threads:[~2020-02-26 14:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 13:38 [GIT PULL v2] EFI updates for v5.7 Ard Biesheuvel
2020-02-26 14:27 ` Ingo Molnar [this message]
2020-02-26 14:50 ` Ard Biesheuvel
2020-02-26 20:45 ` [PATCH 0/1] Small fix to boot-time GDT handling Arvind Sankar
2020-02-26 23:00 ` [PATCH v2 " Arvind Sankar
2020-02-26 23:00 ` [PATCH v2 1/1] x86/boot/compressed: Fix reloading of GDTR post-relocation Arvind Sankar
2020-02-27 8:12 ` Ingo Molnar
2020-02-27 15:16 ` Arvind Sankar
2020-02-27 15:21 ` Ard Biesheuvel
2020-02-27 15:54 ` Arvind Sankar
2020-02-27 17:47 ` Ard Biesheuvel
2020-02-27 18:03 ` Arvind Sankar
2020-02-29 9:24 ` Ingo Molnar
2020-02-29 16:50 ` Arvind Sankar
2020-02-26 20:45 ` [PATCH 1/1] x86/boot/compressed/32: " Arvind Sankar
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=20200226142713.GB3100@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nivedita@alum.mit.edu \
--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).