From: yi1.li@intel.com
To: devel@edk2.groups.io
Cc: yi1 li <yi1.li@intel.com>
Subject: [PATCH 1/1] MdePkg: Fix DEVICE_SECURITY_EVENT_DATA_HEADER version definition
Date: Thu, 23 Sep 2021 09:57:08 +0800 [thread overview]
Message-ID: <f5c719df7fe2d35c5d83114373ecbd1b857dde80.1632360172.git.yi1.li@intel.com> (raw)
In-Reply-To: <cover.1632360172.git.yi1.li@intel.com>
REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3646
According to latest TCG PFP spec 1.05 revision 23,
(https://trustedcomputinggroup.org/resource/pc-client-specific
-platform-firmware-profile-specification/),
10.2.7 DEVICE_SECURITY_EVENT_DATA Structure,
the version should be 1.
Signed-off-by: yi1 li <yi1.li@intel.com>
---
MdePkg/Include/IndustryStandard/UefiTcgPlatform.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MdePkg/Include/IndustryStandard/UefiTcgPlatform.h b/MdePkg/Include/IndustryStandard/UefiTcgPlatform.h
index 84023c434762..d5bc78611704 100644
--- a/MdePkg/Include/IndustryStandard/UefiTcgPlatform.h
+++ b/MdePkg/Include/IndustryStandard/UefiTcgPlatform.h
@@ -275,7 +275,7 @@ typedef struct tdUEFI_GPT_DATA {
} UEFI_GPT_DATA;
#define TCG_DEVICE_SECURITY_EVENT_DATA_SIGNATURE "SPDM Device Sec"
-#define TCG_DEVICE_SECURITY_EVENT_DATA_VERSION 0
+#define TCG_DEVICE_SECURITY_EVENT_DATA_VERSION 1
#define TCG_DEVICE_SECURITY_EVENT_DATA_DEVICE_TYPE_NULL 0
#define TCG_DEVICE_SECURITY_EVENT_DATA_DEVICE_TYPE_PCI 1
--
2.33.0.windows.2
next parent reply other threads:[~2021-09-23 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1632360172.git.yi1.li@intel.com>
2021-09-23 1:57 ` yi1.li [this message]
2021-09-23 2:29 ` [PATCH 1/1] MdePkg: Fix DEVICE_SECURITY_EVENT_DATA_HEADER version definition Yao, Jiewen
2021-09-23 2:41 ` 回复: " gaoliming
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=f5c719df7fe2d35c5d83114373ecbd1b857dde80.1632360172.git.yi1.li@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