From: "Ni, Ray" <ray.ni@intel.com>
To: "Dong, Eric" <eric.dong@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: Laszlo Ersek <lersek@redhat.com>
Subject: Re: [Patch v2 0/2] UefiCpuPkg: Remove debug message.
Date: Mon, 5 Aug 2019 09:21:18 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5C27047D@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190805064359.29332-1-eric.dong@intel.com>
Reviewed-by: Ray Ni <ray.ni@intel.com>
> -----Original Message-----
> From: Dong, Eric
> Sent: Monday, August 5, 2019 2:44 PM
> To: devel@edk2.groups.io
> Cc: Ni, Ray <ray.ni@intel.com>; Laszlo Ersek <lersek@redhat.com>
> Subject: [Patch v2 0/2] UefiCpuPkg: Remove debug message.
>
> This debug message may be called by BSP and APs. It may caused ASSERT
> when APs call this debug code.
>
> In order to avoid system boot assert, Remove this debug message.
>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
>
> Eric Dong (2):
> UefiCpuPkg/RegisterCpuFeaturesLib: Remove debug message.
> UefiCpuPkg/PiSmmCpuDxeSmm: Remove debug message.
>
> .../CpuFeaturesInitialize.c | 22 -------------------
> UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 22 +------------------
> 2 files changed, 1 insertion(+), 43 deletions(-)
>
> --
> 2.21.0.windows.1
next prev parent reply other threads:[~2019-08-05 9:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-05 6:43 [Patch v2 0/2] UefiCpuPkg: Remove debug message Dong, Eric
2019-08-05 6:43 ` [Patch v2 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: " Dong, Eric
2019-08-07 17:17 ` [edk2-devel] " rebecca
2019-08-08 18:53 ` Laszlo Ersek
2019-08-05 6:43 ` [Patch v2 2/2] UefiCpuPkg/PiSmmCpuDxeSmm: " Dong, Eric
2019-08-05 9:21 ` Ni, Ray [this message]
2019-08-07 17:11 ` [Patch v2 0/2] UefiCpuPkg: " Laszlo Ersek
2019-08-07 18:14 ` Laszlo Ersek
2019-08-08 0:07 ` Dong, Eric
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=734D49CCEBEEF84792F5B80ED585239D5C27047D@SHSMSX104.ccr.corp.intel.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