From: "Zhou, Bowen" <bowen.zhou@intel.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: [PATCH] PurleyOpenBoardPkg: fix build error
Date: Tue, 25 Sep 2018 07:25:01 +0000 [thread overview]
Message-ID: <477DBD36544FF849A8AD024E912EEC0F58FFC120@SHSMSX101.ccr.corp.intel.com> (raw)
Fix format error of gEfiPchSetTmcSrcClkProtocolGuid in PchRcPkg.dec.
Build error is:
error 3000: Invalid GUID value format
gEfiPchSetTmcSrcClkProtocolGuid = {0xfbaa2549, 0x53d, 0x4012, 0x86, 0x6c, 0x7a, 0x86, 0xcc, 0x21, 0xae, 0x21} (<CName> = <GuidValueInCFormat:{8,4,4,{2,2,2,2,2,2,2,2}}>)
Cc: Jiewen Yao <jiewen.yao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.1
Signed-off-by: Xiaohu Zhou <bowen.zhou@intel.com>
---
Silicon/Intel/LewisburgPkg/PchRcPkg.dec | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Silicon/Intel/LewisburgPkg/PchRcPkg.dec b/Silicon/Intel/LewisburgPkg/PchRcPkg.dec
index 69ec66f1c2..441d9e75e3 100644
--- a/Silicon/Intel/LewisburgPkg/PchRcPkg.dec
+++ b/Silicon/Intel/LewisburgPkg/PchRcPkg.dec
@@ -101,7 +101,7 @@
gPchResetProtocolGuid = { 0xdb63592c, 0xb8cc, 0x44c8, { 0x91, 0x8c, 0x51, 0xf5, 0x34, 0x59, 0x8a, 0x5a}}
gEfiGlobalNvsAreaProtocolGuid = {0x74e1e48, 0x8132, 0x47a1, { 0x8c, 0x2c, 0x3f, 0x14, 0xad, 0x9a, 0x66, 0xdc }}
gPchSmmIoTrapControlGuid = {0x514D2AFD, 0x2096, 0x4283, {0x9D, 0xA6, 0x70, 0x0C, 0xD2, 0x7D, 0xC7, 0xA5 }}
- gEfiPchSetTmcSrcClkProtocolGuid = {0xfbaa2549, 0x53d, 0x4012, 0x86, 0x6c, 0x7a, 0x86, 0xcc, 0x21, 0xae, 0x21}
+ gEfiPchSetTmcSrcClkProtocolGuid = {0xfbaa2549, 0x53d, 0x4012, {0x86, 0x6c, 0x7a, 0x86, 0xcc, 0x21, 0xae, 0x21}}
gPchPlatformPolicyProtocolGuid = { 0x782ee5ae, 0x586b, 0x47c1, { 0xa4, 0x1d, 0xce, 0x7f, 0xa0, 0x9c, 0x25, 0x9a }}
gPchInfoProtocolGuid = { 0x984eb4e9, 0x5a95, 0x41de, {0xaa, 0xd0, 0x53, 0x66, 0x8c, 0xa5, 0x13, 0xc0}}
gPchNvsAreaProtocolGuid = {0x2E058B2B, 0xEDC1, 0x4431, {0x87, 0xD9, 0xC6, 0xC4, 0xEA, 0x10, 0x2B, 0xE3 }}
--
2.14.3.windows.1
reply other threads:[~2018-09-25 7:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=477DBD36544FF849A8AD024E912EEC0F58FFC120@SHSMSX101.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