From: "Laszlo Ersek" <lersek@redhat.com>
To: sergei@posteo.net
Cc: devel@edk2.groups.io, Ray Ni <ray.ni@intel.com>,
Zhichao Gao <zhichao.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 0/2] "maybe-uninitialized" warnings emitted by
Date: Fri, 14 May 2021 12:01:45 +0200 [thread overview]
Message-ID: <a62e0ae4-14ad-1935-32d5-b5f59af51637@redhat.com> (raw)
In-Reply-To: <20210511225616.5942-1-sergei@posteo.net>
On 05/12/21 00:56, Sergei Dmitrouk wrote:
> Compiling for IA32 target with gcc-5.5.0 emits "maybe-uninitialized" warnings.
> Compilation command: build -a IA32 -p OvmfPkg/OvmfPkgIa32.dsc -t GCC49
>
> Sergei Dmitrouk (2):
> ShellPkg/UefiShellCommandLib: suppress incorrect gcc warning
> OvmfPkg/VirtioFsDxe: suppress incorrect gcc warnings
>
> OvmfPkg/VirtioFsDxe/SimpleFsOpen.c | 11 +++++++++++
> .../Library/UefiShellCommandLib/UefiShellCommandLib.c | 5 +++++
> 2 files changed, 16 insertions(+)
>
Merged as commit range 22ac5cc9d9db..d82c4693f8d5, via
<https://github.com/tianocore/edk2/pull/1643>.
I've gone ahead and merged the ShellPkg patch too, with only my R-b. I
had written the original code, and I've carefully verified Sergei's
patch too. Sergei learned the edk2 contribution process, and got it
right, at the first posting attempt; I wouldn't like to make him wait
several days for a ShellPkg ACK, with such a small patch.
Thanks for the contribution!
Laszlo
prev parent reply other threads:[~2021-05-14 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 22:56 [PATCH v1 0/2] "maybe-uninitialized" warnings emitted by sergei
2021-05-11 22:56 ` [PATCH v1 1/2] ShellPkg/UefiShellCommandLib: suppress incorrect gcc warning Sergei Dmitrouk
2021-05-14 9:19 ` [edk2-devel] " Laszlo Ersek
2021-05-11 22:56 ` [PATCH v1 2/2] OvmfPkg/VirtioFsDxe: suppress incorrect gcc warnings Sergei Dmitrouk
2021-05-14 9:29 ` [edk2-devel] " Laszlo Ersek
2021-05-14 10:01 ` Laszlo Ersek [this message]
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=a62e0ae4-14ad-1935-32d5-b5f59af51637@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