public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Wang, Jian J" <jian.j.wang@intel.com>
To: "Bi, Dandan" <dandan.bi@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Dong, Eric" <eric.dong@intel.com>, Laszlo Ersek <lersek@redhat.com>
Subject: Re: [PATCH 3/4] UefiCpuPkg/UefiCpuPkg.uni: Add missing string definition for new PCDs
Date: Mon, 25 Dec 2017 02:28:21 +0000	[thread overview]
Message-ID: <D827630B58408649ACB04F44C510003624CC2FF3@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <3C0D5C461C9E904E8F62152F6274C0BB3B9F051C@SHSMSX103.ccr.corp.intel.com>

Sure. Thanks.

Regards,
Jian


> -----Original Message-----
> From: Bi, Dandan
> Sent: Monday, December 25, 2017 9:59 AM
> To: Wang, Jian J <jian.j.wang@intel.com>; edk2-devel@lists.01.org
> Cc: Dong, Eric <eric.dong@intel.com>; Laszlo Ersek <lersek@redhat.com>
> Subject: RE: [PATCH 3/4] UefiCpuPkg/UefiCpuPkg.uni: Add missing string
> definition for new PCDs
> 
> Hi Jian,
> 
> Could you add the "string" keyword before the string token when you commit
> the patch. You can refer to other codes in the uni file.
> With this update, Reviewed-by: Dandan Bi <dandan.bi@intel.com>
> 
> Thanks,
> Dandan
> -----Original Message-----
> From: Wang, Jian J
> Sent: Monday, December 25, 2017 9:07 AM
> To: edk2-devel@lists.01.org
> Cc: Bi, Dandan <dandan.bi@intel.com>; Dong, Eric <eric.dong@intel.com>;
> Laszlo Ersek <lersek@redhat.com>
> Subject: [PATCH 3/4] UefiCpuPkg/UefiCpuPkg.uni: Add missing string definition
> for new PCDs
> 
> Cc: Dandan Bi <dandan.bi@intel.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Laszlo Ersek <lersek@redhat.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
> ---
>  UefiCpuPkg/UefiCpuPkg.uni | 16 ++++++++++++++--
>  1 file changed, 14 insertions(+), 2 deletions(-)
> 
> diff --git a/UefiCpuPkg/UefiCpuPkg.uni b/UefiCpuPkg/UefiCpuPkg.uni index
> a7073b10c8..6fcfc6e7f2 100644
> --- a/UefiCpuPkg/UefiCpuPkg.uni
> +++ b/UefiCpuPkg/UefiCpuPkg.uni
> @@ -230,5 +230,17 @@
>                                                                                          "Processor trace is enabled
> through set BIT44(CPU_FEATURE_PROC_TRACE) in
> PcdCpuFeaturesSetting.<BR><BR>\n"
>                                                                                          "This PCD is ignored if CPU
> processor trace is disabled.<BR><BR>\n"
>                                                                                          "Default value is 0 which means
> single range output scheme will be used if CPU processor trace is
> enabled.<BR>\n"
> -                                                                                        "0 - Single Range output
> scheme.<BR>\n"
> 
> -                                                                                        "1 - ToPA(Table of physical
> address) scheme.<BR>\n"
> \ No newline at end of file
> +                                                                                        "0 - Single Range output
> scheme.<BR>\n"
> +                                                                                        "1 - ToPA(Table of physical
> address) scheme.<BR>\n"
> +
> +#STR_gUefiCpuPkgTokenSpaceGuid_PcdCpuStackSwitchExceptionList_PROMP
> T  #language en-US "Specify exception vectors which need switching stack."
> +
> +#STR_gUefiCpuPkgTokenSpaceGuid_PcdCpuStackSwitchExceptionList_HELP
> #language en-US "List of exception vectors which need switching stack.\n"
> +                                                                                    "This PCD will only take into
> effect if PcdCpuStackGuard is enabled.n"
> +                                                                                    "By default exception #DD(8),
> #PF(14) are supported.n"
> +
> +#STR_gUefiCpuPkgTokenSpaceGuid_PcdCpuKnownGoodStackSize_PROMPT
> #language en-US "Specify size of good stack of exception which need switching
> stack."
> +
> +#STR_gUefiCpuPkgTokenSpaceGuid_PcdCpuKnownGoodStackSize_HELP
> #language en-US "Size of good stack for an exception.\n"
> +                                                                              "This PCD will only take into effect if
> PcdCpuStackGuard is enabled.\n"
> +
> --
> 2.15.1.windows.2



  reply	other threads:[~2017-12-25  2:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-25  1:06 [PATCH 0/4] Coding style clean-up Jian J Wang
2017-12-25  1:06 ` [PATCH 1/4] MdePkg/BaseLib.h: " Jian J Wang
2017-12-25  1:51   ` Bi, Dandan
2017-12-25  2:23     ` Wang, Jian J
2017-12-25  1:06 ` [PATCH 2/4] MdeModulePkg/Core: " Jian J Wang
2017-12-25  1:19   ` Zeng, Star
2017-12-25  2:01   ` Bi, Dandan
2017-12-25  1:06 ` [PATCH 3/4] UefiCpuPkg/UefiCpuPkg.uni: Add missing string definition for new PCDs Jian J Wang
2017-12-25  1:58   ` Bi, Dandan
2017-12-25  2:28     ` Wang, Jian J [this message]
2017-12-25  1:06 ` [PATCH 4/4] UefiCpuPkg: Update code to use new structure field names Jian J Wang
2017-12-25  2:01   ` Bi, Dandan
2017-12-26 16:47 ` [PATCH 0/4] Coding style clean-up Kinney, Michael D
2017-12-27  0:40   ` Wang, Jian J
2017-12-27  9:29     ` Gao, Liming
2017-12-27 16:35     ` Kinney, Michael D
2017-12-28  0:27       ` Wang, Jian J
2017-12-28  0:37         ` Kinney, Michael D
2017-12-28  0:53           ` Wang, Jian J

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=D827630B58408649ACB04F44C510003624CC2FF3@SHSMSX103.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