From: "Laszlo Ersek" <lersek@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
edk2-devel-groups-io <devel@edk2.groups.io>
Cc: "Jordan Justen" <jordan.l.justen@intel.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg/X86QemuLoadImageLib: fix "unused variable" error in X64 DXE builds
Date: Sun, 8 Mar 2020 10:40:48 +0100 [thread overview]
Message-ID: <4e32dfd7-a4f7-4644-654a-24b72dda9416@redhat.com> (raw)
In-Reply-To: <CAKv+Gu91JVLDMziOJO7B2+rpbEbAktU1dWFWAb32-p0e_uHHNQ@mail.gmail.com>
On 03/07/20 15:34, Ard Biesheuvel wrote:
> On Sat, 7 Mar 2020 at 00:04, Laszlo Ersek <lersek@redhat.com> wrote:
>>
>> When the MDE_CPU_IA32 macro is not defined, there is no access to the
>> "KernelImageHandle" local variable in QemuStartKernelImage(). This breaks
>> the OvmfPkgIa32X64 and OvmfPkgX64 platform builds, at least with gcc-8.
>>
>> Move the local variable to the inner scope, where declaration and usage
>> are inseparable.
>>
>> (Note that such inner-scope declarations are frowned upon in the wider
>> edk2 codebase, but we use them liberally in ArmVirtPkg and OvmfPkg anyway,
>> because they help us reason about variable lifetime and visibility.)
>>
>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
>> Fixes: 7c47d89003a6f8f7f6f0ce8ca7d3e87c630d14cc
>> Ref: https://bugzilla.tianocore.org/show_bug.cgi?id=2572
>> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
>
> Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>
> (in case you still need it)
Thanks. If the workaround for the current github / mergify outage turns
out to be "resubmit pending PRs", then I'll likely pick up your R-b too.
Seeing how your latest <https://github.com/tianocore/edk2/pull/430> is
also stuck, I must wonder what is going on at github. They have not
responded to my ticket (592107) and their status page claims "All
Systems Operational":
https://www.githubstatus.com/
Which is not the case.
Mergify have their own status page:
https://www.notion.so/Mergify-Status-Page-7803a762235d4ee6bed1f9976d17bd83
and that also claims "Dashboard Operational" and "Engine Operational".
I've now sent an email to <support@mergify.io> too.
Laszlo
next prev parent reply other threads:[~2020-03-08 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 23:04 [PATCH] OvmfPkg/X86QemuLoadImageLib: fix "unused variable" error in X64 DXE builds Laszlo Ersek
2020-03-07 0:01 ` Philippe Mathieu-Daudé
2020-03-07 1:00 ` [edk2-devel] " Laszlo Ersek
2020-03-07 6:10 ` Ard Biesheuvel
2020-03-07 7:28 ` Laszlo Ersek
2020-03-07 7:41 ` Laszlo Ersek
2020-03-07 14:34 ` Ard Biesheuvel
2020-03-08 9:40 ` Laszlo Ersek [this message]
2020-03-09 23:19 ` Laszlo Ersek
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-list 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=4e32dfd7-a4f7-4644-654a-24b72dda9416@redhat.com \
--to=devel@edk2.groups.io \
/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