From: "Wu, Hao A" <hao.a.wu@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"kun.q@outlook.com" <kun.q@outlook.com>
Subject: Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface
Date: Sun, 7 Feb 2021 00:44:31 +0000 [thread overview]
Message-ID: <BN8PR11MB3666E0967E021840EB77DC2CCAB09@BN8PR11MB3666.namprd11.prod.outlook.com> (raw)
In-Reply-To: <25624.1612579703339748215@groups.io>
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Hello Kun,
Could you help to send the library interface together with its usage in modules in the series?
Thanks in advance.
Also, one more question is that are Tcg2Smm and VariableSmmRuntimeDxe the only modules need to be updated?
Or an investigation in the code base should be done to address all the potential modules affected?
Best Regards,
Hao Wu
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Kun Qin
Sent: Saturday, February 6, 2021 10:48 AM
To: Wu; Wu, Hao A <hao.a.wu@intel.com>; devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface
Hi Hao,
My plan was to follow up with the driver changes regarding Tcg2Smm and VariableSmmRuntimeDxe once this interface is officially checked in. But if it is preferred to submit the patch for Tcg2Smm and VariableSmmRuntimeDxe to make better sense on how this interface will be consumed, I can send them out in v2. Please let me know how you would like to proceed.
Thanks,
Kun
[-- Attachment #2: Type: text/html, Size: 3717 bytes --]
next prev parent reply other threads:[~2021-02-07 0:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 22:16 [PATCH v1 0/1] Introduce DxeMmUnblockMemoryLib Interface Kun Qin
2021-02-05 2:17 ` [edk2-devel] " Wu, Hao A
2021-02-05 2:37 ` Sean
2021-02-05 2:52 ` Wu, Hao A
2021-02-05 3:10 ` Kun Qin
2021-02-05 7:11 ` Wu, Hao A
2021-02-06 2:48 ` Kun Qin
2021-02-07 0:44 ` Wu, Hao A [this message]
2021-02-08 18:15 ` Kun Qin
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=BN8PR11MB3666E0967E021840EB77DC2CCAB09@BN8PR11MB3666.namprd11.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