> > This driver is now both the producer and consumer of > gEdkiiMemoryAcceptProtocolGuid. > > Are there cases where the protocol we locate here could be different > from the one installed by this driver? If not, we can simplify this, > and just call AmdSevMemoryAccept() directly. >
Ah right. There should not be another implementation. I can make that change. -- -Dionna Glaze, PhD (she/her) -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#99085): https://edk2.groups.io/g/devel/message/99085 Mute This Topic: https://groups.io/mt/96534752/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
