public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
	"Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Jordan Justen" <jordan.l.justen@intel.com>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg/X86QemuLoadImageLib: fix "unused variable" error in X64 DXE builds
Date: Sat, 7 Mar 2020 07:10:04 +0100	[thread overview]
Message-ID: <CAKv+Gu_F-0GF_YPNQ6+GZyZ64Jd0ivdd_xO2yeL-UGO3kWxx-w@mail.gmail.com> (raw)
In-Reply-To: <2fd1019a-4947-05c9-874a-0faa863454b9@redhat.com>

On Sat, 7 Mar 2020 at 02:00, Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 03/07/20 01:01, Philippe Mathieu-Daudé wrote:
> > On 3/7/20 12:04 AM, Laszlo Ersek 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: Philippe Mathieu-Daude <philmd@redhat.com>
> > Tested-by: Philippe Mathieu-Daude <philmd@redhat.com>
>
> Thank you, Phil, this really helps -- I want to push the patch as
> quickly as possible, due to it averting a build break.
>
> So I've submitted <https://github.com/tianocore/edk2/pull/428> with your
> tags applied... but mergify is apparently not picking up the "push"
> label again... I have no idea what's going on.
>

I queued it here as well:
https://github.com/tianocore/edk2/pull/427

  reply	other threads:[~2020-03-07  6:10 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 [this message]
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
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=CAKv+Gu_F-0GF_YPNQ6+GZyZ64Jd0ivdd_xO2yeL-UGO3kWxx-w@mail.gmail.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