From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: edk2-devel-01 <edk2-devel@lists.01.org>,
"Zhang, Chao B" <chao.b.zhang@intel.com>
Subject: Re: [PATCH 2/2] SecurityPkg/TcgPei: drop PeiReadOnlyVariable from Depex
Date: Fri, 9 Mar 2018 23:12:12 +0000 [thread overview]
Message-ID: <1842DC23-4097-462F-A4EF-A0F951166FC1@intel.com> (raw)
In-Reply-To: <20180309200525.27376-3-lersek@redhat.com>
reviewed by: jiewen.yao@intel.com
thank you!
Yao, Jiewen
> 在 2018年3月10日，上午4:05，Laszlo Ersek <lersek@redhat.com> 写道：
>
> TcgPei doesn't actually use the PEI-phase read-only variable service, so
> drop that from the Depex.
>
> This patch was inspired by commit ab9e11da6651 ("SecurityPkg/Tcg2Pei: drop
> PeiReadOnlyVariable from Depex", 2018-03-09).
>
> Cc: Chao Zhang <chao.b.zhang@intel.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Suggested-by: Chao Zhang <chao.b.zhang@intel.com>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> ---
> SecurityPkg/Tcg/TcgPei/TcgPei.inf | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/SecurityPkg/Tcg/TcgPei/TcgPei.inf b/SecurityPkg/Tcg/TcgPei/TcgPei.inf
> index 9a44d8fbda51..57ce7263e909 100644
> --- a/SecurityPkg/Tcg/TcgPei/TcgPei.inf
> +++ b/SecurityPkg/Tcg/TcgPei/TcgPei.inf
> @@ -85,7 +85,6 @@ [Pcd]
>
> [Depex]
> gEfiPeiMasterBootModePpiGuid AND
> - gEfiPeiReadOnlyVariable2PpiGuid AND
> gEfiTpmDeviceSelectedGuid
>
> [UserExtensions.TianoCore."ExtraFiles"]
> --
> 2.14.1.3.gb7cf6e02401b
>
next prev parent reply other threads:[~2018-03-09 23:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 20:05 [PATCH 0/2] OvmfPkg, SecurityPkg: small followup patches after the TPM2 addition to OVMF Laszlo Ersek
2018-03-09 20:05 ` [PATCH 1/2] OvmfPkg/Tcg2ConfigPei: trivial coding style updates Laszlo Ersek
2018-03-09 20:05 ` [PATCH 2/2] SecurityPkg/TcgPei: drop PeiReadOnlyVariable from Depex Laszlo Ersek
2018-03-09 23:12 ` Yao, Jiewen [this message]
2018-03-13 1:20 ` Zhang, Chao B
2018-03-09 23:50 ` [PATCH 0/2] OvmfPkg, SecurityPkg: small followup patches after the TPM2 addition to OVMF Jordan Justen
2018-03-10 15:34 ` Laszlo Ersek
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=1842DC23-4097-462F-A4EF-A0F951166FC1@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