From: "Laszlo Ersek" <lersek@redhat.com>
To: Shenglei Zhang <shenglei.zhang@intel.com>, devel@edk2.groups.io
Cc: Eric Dong <eric.dong@intel.com>, Ray Ni <ray.ni@intel.com>
Subject: Re: [PATCH 1/1] UefiCpuPkg/PiSmmCpuDxeSmm: Fix coding style
Date: Wed, 7 Aug 2019 18:00:03 +0200 [thread overview]
Message-ID: <4d0d707a-5ada-74e1-c99c-ca19edb38fb0@redhat.com> (raw)
In-Reply-To: <20190807020902.9972-1-shenglei.zhang@intel.com>
On 08/07/19 04:09, Shenglei Zhang wrote:
> 1. Update CPUStatus to CpuStatus in comments to align comments
> with code.
> 2. Add "OUT" attribute for "ProcedureArguments" parameter in function
> header.
>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Signed-off-by: Shenglei Zhang <shenglei.zhang@intel.com>
> ---
> UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h b/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h
> index a0e59f20886b..7b3fbc8b55ec 100644
> --- a/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h
> +++ b/UefiCpuPkg/PiSmmCpuDxeSmm/PiSmmCpuDxeSmm.h
> @@ -1311,7 +1311,7 @@ RestoreCr2 (
> Note that timeout support is optional. Whether an implementation
> supports this feature can be determined via the Attributes data
> member.
> - @param[in,out] CPUStatus This optional pointer may be used to get the status code returned
> + @param[in,out] CpuStatus This optional pointer may be used to get the status code returned
> by Procedure when it completes execution on the target AP, or with
> EFI_TIMEOUT if the Procedure fails to complete within the optional
> timeout. The implementation will update this variable with
> @@ -1437,8 +1437,8 @@ InternalSmmStartupAllAPs (
> **/
> EFI_STATUS
> RegisterStartupProcedure (
> - IN EFI_AP_PROCEDURE Procedure,
> - IN VOID *ProcedureArguments OPTIONAL
> + IN EFI_AP_PROCEDURE Procedure,
> + IN OUT VOID *ProcedureArguments OPTIONAL
> );
>
> /**
>
scrambling to wade through my email backlog after being away for a few
days, so I'm skipping this
thanks
Laszlo
prev parent reply other threads:[~2019-08-07 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-07 2:09 [PATCH 1/1] UefiCpuPkg/PiSmmCpuDxeSmm: Fix coding style Zhang, Shenglei
2019-08-07 16:00 ` 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=4d0d707a-5ada-74e1-c99c-ca19edb38fb0@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