From: Laszlo Ersek <lersek@redhat.com>
To: Anthony PERARD <anthony.perard@citrix.com>, edk2-devel@lists.01.org
Cc: Eric Dong <eric.dong@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
Dandan Bi <dandan.bi@intel.com>
Subject: Re: [PATCH v2] UefiCpuPkg/MpInitLib: Fix build of Microcode
Date: Thu, 19 Jul 2018 20:32:48 +0200 [thread overview]
Message-ID: <caf6caa0-bd0e-3822-6d85-769c2c63f513@redhat.com> (raw)
In-Reply-To: <20180719155220.7344-1-anthony.perard@citrix.com>
Hi Anthony,
(I'm seeing your v1 and v2 postings at the same time now:)
On 07/19/18 17:52, Anthony PERARD wrote:
> On Debian Jessie, this fail to build with:
>
> /build/UefiCpuPkg/Library/MpInitLib/Microcode.c: In function 'MicrocodeDetect':
> /build/UefiCpuPkg/Library/MpInitLib/Microcode.c:248:37: error: 'ProcessorFlags' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> CpuMpData->ProcessorFlags = ProcessorFlags;
> ^
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> ---
>
> Notes:
> v2:
> Fix coding style.
>
> UefiCpuPkg/Library/MpInitLib/Microcode.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/UefiCpuPkg/Library/MpInitLib/Microcode.c b/UefiCpuPkg/Library/MpInitLib/Microcode.c
> index efda143e67..cea1d34c0a 100644
> --- a/UefiCpuPkg/Library/MpInitLib/Microcode.c
> +++ b/UefiCpuPkg/Library/MpInitLib/Microcode.c
> @@ -87,6 +87,7 @@ MicrocodeDetect (
> }
>
> ExtendedTableLength = 0;
> + ProcessorFlags = 0;
> //
> // Here data of CPUID leafs have not been collected into context buffer, so
> // GetProcessorCpuid() cannot be used here to retrieve CPUID data.
>
a patch for fixing this issue is on its way to being committed (Dandan
posted it just ~10 hours before your v1). Please see the thread
[edk2] [patch] UefiCpuPkg/MpInitLib: Fix VS2012 build failure
http://mid.mail-archive.com/20180719045059.55868-1-dandan.bi@intel.com
I think when Liming commented on your v1, he was unaware of Dandan's
patch. And, I'm seeing your v1+v2 just now, at the same time. Sorry
about the inconvenience!
Thanks
Laszlo
next prev parent reply other threads:[~2018-07-19 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-19 14:58 [PATCH] UefiCpuPkg/MpInitLib: Fix build of Microcode Anthony PERARD
2018-07-19 15:27 ` Gao, Liming
2018-07-19 15:52 ` [PATCH v2] " Anthony PERARD
2018-07-19 18:32 ` Laszlo Ersek [this message]
2018-07-20 9:42 ` Anthony PERARD
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=caf6caa0-bd0e-3822-6d85-769c2c63f513@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