From: "Sean" <spbrogan@outlook.com>
To: Stefan Berger <stefanb@linux.ibm.com>,
devel@edk2.groups.io, stefanb@linux.vnet.ibm.com,
jiewen.yao@intel.com
Cc: marcandre.lureau@redhat.com, lersek@redhat.com,
dick_wilkins@phoenix.com, James.Bottomley@HansenPartnership.com
Subject: Re: [edk2-devel] [PATCH v4 1/6] OvmfPkg/TPM: Import PeiDxeTpmPlatformHierarchyLib.c from edk2-platforms
Date: Fri, 13 Aug 2021 11:47:06 -0700 [thread overview]
Message-ID: <BY3PR19MB49008FF1BABE62949C2AE596C8FA9@BY3PR19MB4900.namprd19.prod.outlook.com> (raw)
In-Reply-To: <649733db-0d37-326e-5f83-f6f8ad500cdd@linux.ibm.com>
Thanks for the link as i missed that message.
To me this just points out more problems with how OVMF is being managed
in the edk2 project and the uselessness of edk2 platforms as anything
more than just a dumping ground repo to hold sample code. But that is a
problem larger than this patchset.
I guess if you are going doing option 2 can we rename the library
interface you are defining in OvmfPkg so it doesn't conflict with the
existing one in edk2-platforms/minplatform. That would mean change:
* name in OvmfPkg.dec file
* header file in OvmfPkg/Include/Library
* all references in DSC file for mapping an instance
* all references in your INFs for dependency
Thanks
Sean
On 8/12/2021 3:19 PM, Stefan Berger wrote:
>
> On 8/12/21 4:59 PM, Sean Brogan wrote:
>> This seems like a bad place for a general purpose lib that many other
>> platforms may take a dependency on.
>>
>> In v1 this was SecurityPkg. OvmfPkg is a platform package and
>> therefore not a good place to define broad interfaces.
>>
>> What caused this to move here?
>
>
> Option 2 from this message:
> https://listman.redhat.com/archives/edk2-devel-archive/2021-August/msg00398.html
>
>
> Stefan
>
>
>>
>> Thanks
>> Sean
>>
>>
next prev parent reply other threads:[~2021-08-13 18:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 16:59 [PATCH v4 0/6] Ovmf: Disable the TPM2 platform hierarchy Stefan Berger
2021-08-12 16:59 ` [PATCH v4 1/6] OvmfPkg/TPM: Import PeiDxeTpmPlatformHierarchyLib.c from edk2-platforms Stefan Berger
2021-08-12 20:59 ` [edk2-devel] " Sean
2021-08-12 22:19 ` Stefan Berger
2021-08-13 18:47 ` Sean [this message]
2021-08-13 19:02 ` Stefan Berger
2021-08-14 13:28 ` Marvin Häuser
2021-08-12 16:59 ` [PATCH v4 2/6] OvmfPkg/TPM: Add a NULL implementation of TpmPlatformHierarchyLib Stefan Berger
2021-08-12 16:59 ` [PATCH v4 3/6] OvmfPkg: Reference new TPM classes in the build system for compilation Stefan Berger
2021-08-12 16:59 ` [PATCH v4 4/6] OvmfPkg: Disable the TPM2 platform hierarchy Stefan Berger
2021-08-12 16:59 ` [PATCH v4 5/6] ArmVirtPkg: Reference new TPM classes in the build system for compilation Stefan Berger
2021-08-12 16:59 ` [PATCH v4 6/6] ArmVirtPkg: Disable the TPM2 platform hierarchy Stefan Berger
2021-08-13 12:32 ` [PATCH v4 0/6] Ovmf: " Stefan Berger
2021-08-14 13:01 ` Yao, Jiewen
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=BY3PR19MB49008FF1BABE62949C2AE596C8FA9@BY3PR19MB4900.namprd19.prod.outlook.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