From: Ard Biesheuvel <ardb@kernel.org>
To: Russell King - ARM Linux admin <linux@armlinux.org.uk>
Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>,
linux-efi <linux-efi@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Marc Zyngier <maz@kernel.org>, Chen-Yu Tsai <wens@csie.org>
Subject: Re: [PATCH v2 1/2] efi/arm: decompressor: deal with HYP mode boot gracefully
Date: Fri, 12 Jun 2020 00:39:08 +0200 [thread overview]
Message-ID: <CAMj1kXE+y=Q+-wZaPT6ap278OfP2wbBM3CCvyHCL9K=AaBbO=A@mail.gmail.com> (raw)
In-Reply-To: <20200611223800.GZ1551@shell.armlinux.org.uk>
On Fri, 12 Jun 2020 at 00:38, Russell King - ARM Linux admin
<linux@armlinux.org.uk> wrote:
>
> On Fri, Jun 12, 2020 at 12:18:43AM +0200, Ard Biesheuvel wrote:
> > I've given this a spin myself on a RPi4 running 32-bit U-boot, and
> > everything works as expected, both with and without the GRUB hack
> > enabled.
> >
> > Russell, given that this only affects code inside #ifdef
> > CONFIG_EFI_STUB, do you have any objections to me taking this as a fix
> > via the EFI tree? I have a set of fixes I need to queue up and send
> > out anyway, and I intend to do so early next week.
>
> Please don't, I'll be basing my branches off -rc1 (as normal), and if
> you then submit this as a fix through the EFI tree for merging after
> rc1, and then send me further EFI work to go through the ARM tree,
> we'll end up in exactly the same merge issues as we did prior to this
> merge window.
>
Fair enough. What do you suggest instead? Shall I drop this into the
patch system?
next prev parent reply other threads:[~2020-06-11 22:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 13:58 [PATCH v2 0/2] efi/arm: deal with HYP mode boot Ard Biesheuvel
2020-06-07 13:58 ` [PATCH v2 1/2] efi/arm: decompressor: deal with HYP mode boot gracefully Ard Biesheuvel
2020-06-07 17:24 ` Heinrich Schuchardt
2020-06-07 23:08 ` Ard Biesheuvel
2020-06-08 3:49 ` Chen-Yu Tsai
2020-06-08 10:46 ` Heinrich Schuchardt
2020-06-08 10:59 ` Ard Biesheuvel
2020-06-09 7:58 ` Ard Biesheuvel
2020-06-11 22:18 ` Ard Biesheuvel
2020-06-11 22:38 ` Russell King - ARM Linux admin
2020-06-11 22:39 ` Ard Biesheuvel [this message]
2020-06-11 22:43 ` Russell King - ARM Linux admin
2020-06-11 23:17 ` Ard Biesheuvel
2020-06-07 13:58 ` [PATCH v2 2/2] efi/arm: libstub: print boot mode and MMU state at boot 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='CAMj1kXE+y=Q+-wZaPT6ap278OfP2wbBM3CCvyHCL9K=AaBbO=A@mail.gmail.com' \
--to=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=wens@csie.org \
--cc=xypron.glpk@gmx.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 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).