From: "Wang, Jian J" <jian.j.wang@intel.com>
To: devel@edk2.groups.io
Cc: Chao Zhang <chao.b.zhang@intel.com>, Jiewen Yao <jiewen.yao@intel.com>
Subject: [PATCH v2 3/3] SecurityPkg: add FvReportPei.inf in dsc for build validation
Date: Tue, 11 Jun 2019 02:35:36 +0800 [thread overview]
Message-ID: <20190610183536.5628-4-jian.j.wang@intel.com> (raw)
In-Reply-To: <20190610183536.5628-1-jian.j.wang@intel.com>
https://bugzilla.tianocore.org/show_bug.cgi?id=1617
Cc: Chao Zhang <chao.b.zhang@intel.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
---
SecurityPkg/SecurityPkg.dsc | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/SecurityPkg/SecurityPkg.dsc b/SecurityPkg/SecurityPkg.dsc
index a2ee0528f0..4451bd1271 100644
--- a/SecurityPkg/SecurityPkg.dsc
+++ b/SecurityPkg/SecurityPkg.dsc
@@ -287,6 +287,11 @@
SecurityPkg/HddPassword/HddPasswordDxe.inf
SecurityPkg/HddPassword/HddPasswordPei.inf
+ #
+ # Common FV checker/verifier/reporter
+ #
+ SecurityPkg/FvReportPei/FvReportPei.inf
+
[BuildOptions]
MSFT:*_*_IA32_DLINK_FLAGS = /ALIGN:256
INTEL:*_*_IA32_DLINK_FLAGS = /ALIGN:256
--
2.17.1.windows.2
next prev parent reply other threads:[~2019-06-10 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 18:35 [PATCH v2 0/3] Common OBB verification feature Wang, Jian J
2019-06-10 18:35 ` [PATCH v2 1/3] SecurityPkg: add definitions for OBB verification Wang, Jian J
2019-06-10 18:35 ` [PATCH v2 2/3] SecurityPkg/FvReportPei: implement a common FV verifier and reporter Wang, Jian J
2019-06-10 18:35 ` Wang, Jian J [this message]
2019-06-12 4:48 ` [PATCH v2 0/3] Common OBB verification feature Yao, Jiewen
2019-06-14 0:29 ` Wang, Jian J
2019-06-14 10:41 ` Yao, Jiewen
2019-06-14 16:53 ` Wang, Jian J
[not found] ` <15A7E930E191F486.2329@groups.io>
2019-06-14 5:11 ` [edk2-devel] " 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=20190610183536.5628-4-jian.j.wang@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