From: "Laszlo Ersek" <lersek@redhat.com>
To: Eric Dong <eric.dong@intel.com>, devel@edk2.groups.io
Cc: Ray Ni <ray.ni@intel.com>
Subject: Re: [Patch 2/2] UefiCpuPkg/PiSmmCpuDxeSmm: Clean up useless parameter.
Date: Thu, 8 Aug 2019 22:15:43 +0200 [thread overview]
Message-ID: <2c6eb330-e3cd-8463-a236-ae1d93d0a938@redhat.com> (raw)
In-Reply-To: <20190808132442.33936-3-eric.dong@intel.com>
On 08/08/19 15:24, Eric Dong wrote:
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2060
>
> Remove the useless parameter.
>
> Signed-off-by: Eric Dong <eric.dong@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> ---
> UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c b/UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c
> index d20bc4aae6..d8c6b19ead 100644
> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c
> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/CpuS3.c
> @@ -35,7 +35,6 @@ typedef struct {
> // Flags used when program the register.
> //
> typedef struct {
> - volatile UINTN ConsoleLogLock; // Spinlock used to control console.
> volatile UINTN MemoryMappedLock; // Spinlock used to program mmio
> volatile UINT32 *CoreSemaphoreCount; // Semaphore container used to program
> // core level semaphore.
> @@ -1028,7 +1027,6 @@ GetAcpiCpuData (
> ASSERT (mCpuFlags.PackageSemaphoreCount != NULL);
> }
> InitializeSpinLock((SPIN_LOCK*) &mCpuFlags.MemoryMappedLock);
> - InitializeSpinLock((SPIN_LOCK*) &mCpuFlags.ConsoleLogLock);
> }
>
> /**
>
Same comment as for patch #1. With that fixed:
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thanks!
Laszlo
prev parent reply other threads:[~2019-08-08 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 13:24 [Patch 0/2] Clean up useless parmeter Dong, Eric
2019-08-08 13:24 ` [Patch 1/2] UefiCpuPkg/RegisterCpuFeaturesLib: Clean up useless parameter Dong, Eric
2019-08-08 20:15 ` Laszlo Ersek
2019-08-08 13:24 ` [Patch 2/2] UefiCpuPkg/PiSmmCpuDxeSmm: " Dong, Eric
2019-08-08 20:15 ` 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=2c6eb330-e3cd-8463-a236-ae1d93d0a938@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