From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-efi@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Wilfried Klaebe <linux-kernel@lebenslange-mailadresse.de>
Subject: Re: [GIT PULL 0/1] EFI mixed mode fix for v4.18
Date: Wed, 11 Jul 2018 12:13:03 +0200 [thread overview]
Message-ID: <20180711101303.GA8574@gmail.com> (raw)
In-Reply-To: <20180711090235.9327-1-ard.biesheuvel@linaro.org>
* Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
> The following changes since commit 1e4b044d22517cae7047c99038abb444423243ca:
>
> Linux 4.18-rc4 (2018-07-08 16:34:02 -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 d7f2e972e702d329fe11d6956df99dfc31211c25:
>
> efi/x86: remove pointless call to PciIo->Attributes() (2018-07-11 10:52:46 +0200)
>
> ----------------------------------------------------------------
> A single fix for the x86 PCI I/O protocol handling code that got
> broken for mixed mode (64-bit Linux/x86 on 32-bit UEFI) after a
> fix was applied in -rc2 to fix it for ordinary 64-bit Linux/x86.
Just curious, because it's unclear from the changelog, what was the symptom, a
boot hang, instant reboot, or some other misbehavior? Also, what's the scope of
the fix: were all 64-bit on 32-bit UEFI mixed-mode bootups affected, or only a
certain subset?
Thanks,
Ingo
next prev parent reply other threads:[~2018-07-11 10:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 9:02 [GIT PULL 0/1] EFI mixed mode fix for v4.18 Ard Biesheuvel
2018-07-11 9:02 ` [PATCH 1/1] efi/x86: remove pointless call to PciIo->Attributes() Ard Biesheuvel
2018-07-11 10:13 ` Ingo Molnar [this message]
2018-07-11 10:23 ` [GIT PULL 0/1] EFI mixed mode fix for v4.18 Hans de Goede
2018-07-11 10:24 ` Ard Biesheuvel
2018-07-11 11:14 ` Ingo Molnar
2018-07-11 13:44 ` Ard Biesheuvel
2018-07-11 15:37 ` Ingo Molnar
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=20180711101303.GA8574@gmail.com \
--to=mingo@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=hdegoede@redhat.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@lebenslange-mailadresse.de \
--cc=linux-kernel@vger.kernel.org \
--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 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).