From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>, devel@edk2.groups.io
Cc: lersek@redhat.com,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Stefan Berger" <stefanb@linux.ibm.com>
Subject: Re: [PATCH 0/2] OvmfPkg: clean up TPM2 related DSC/FDF content
Date: Wed, 8 Jan 2020 15:53:25 +0100 [thread overview]
Message-ID: <9d643462-afe2-b059-c2bf-b4f5273f7f6b@redhat.com> (raw)
In-Reply-To: <20200108143843.4198-1-ard.biesheuvel@linaro.org>
Cc'ing Marc-André & Stefan, maintainers of "OvmfPkg: TCG- and
TPM2-related modules".
On 1/8/20 3:38 PM, Ard Biesheuvel wrote:
> Clean up some issues that Laszlo spotted in OVMF while reviewing TPM2
> support for ArmVirtQemu.
>
> Ard Biesheuvel (2):
> OvmfPkg: reorganize TPM2 support in DSC/FDF files
> OvmfPkg: use HII type PCDs for TPM2 config related variables
>
> OvmfPkg/OvmfPkgIa32.dsc | 15 ++++++++++++---
> OvmfPkg/OvmfPkgIa32X64.dsc | 15 ++++++++++++---
> OvmfPkg/OvmfPkgX64.dsc | 9 +++++++++
> OvmfPkg/OvmfPkgIa32.fdf | 3 +++
> OvmfPkg/OvmfPkgIa32X64.fdf | 3 +++
> OvmfPkg/OvmfPkgX64.fdf | 3 +++
> 6 files changed, 42 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2020-01-08 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 14:38 [PATCH 0/2] OvmfPkg: clean up TPM2 related DSC/FDF content Ard Biesheuvel
2020-01-08 14:38 ` [PATCH 1/2] OvmfPkg: reorganize TPM2 support in DSC/FDF files Ard Biesheuvel
2020-01-09 12:38 ` Laszlo Ersek
2020-01-09 12:40 ` Ard Biesheuvel
2020-01-09 12:48 ` Laszlo Ersek
2020-01-08 14:38 ` [PATCH 2/2] OvmfPkg: use HII type PCDs for TPM2 config related variables Ard Biesheuvel
2020-01-09 12:47 ` Laszlo Ersek
2020-01-08 14:53 ` Philippe Mathieu-Daudé [this message]
2020-01-09 13:13 ` [PATCH 0/2] OvmfPkg: clean up TPM2 related DSC/FDF content Ard Biesheuvel
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=9d643462-afe2-b059-c2bf-b4f5273f7f6b@redhat.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