From: "Liming Gao" <liming.gao@intel.com>
To: "Gao, Zhichao" <zhichao.gao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
Vitaly Cheptsov <vit9696@protonmail.com>
Subject: Re: [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib instances
Date: Thu, 12 Dec 2019 05:05:26 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E564B61@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191212020922.14620-1-zhichao.gao@intel.com>
Zhichao:
The change is good. What functionality test is done?
Thanks
Liming
>-----Original Message-----
>From: Gao, Zhichao
>Sent: Thursday, December 12, 2019 10:09 AM
>To: devel@edk2.groups.io
>Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
><liming.gao@intel.com>; Vitaly Cheptsov <vit9696@protonmail.com>
>Subject: [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib
>instances
>
>REF: https://bugzilla.tianocore.org/show_bug.cgi?id=2298
>
>The UefiDevicePathLibOptionalDevicePathProtocolConstructor's
>implementation
>isn't match with its instance name.
>Remove the ASSERT and depex of the gEfiDevicePathUtilitiesProtocolGuid
>because of "Optional".
>
>Add a mandatory instance to force using the DevicePathUtilities,
>DevicePathToText and DevicePathFromText protocol with the ASSERT
>and depex.
>
>V2:
>The optional lib instance's construction should return success all the
>time.
>Change the desciption of the optional lib uni file.
>Change the copyright date of the mandatory one's uni file.
>
>Cc: Michael D Kinney <michael.d.kinney@intel.com>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Vitaly Cheptsov <vit9696@protonmail.com>
>Signed-off-by: Zhichao Gao <zhichao.gao@intel.com>
>
>Zhichao Gao (2):
> MdePkg/UefiDevicePathLib: Separate the device path lib
> MdePkg/dsc: Add UefiDevicePathLibMandatoryDevicePathProtocol for build
>
> ...DevicePathLibMandatoryDevicePathProtocol.c | 469
>++++++++++++++++++
> ...vicePathLibMandatoryDevicePathProtocol.inf | 86 ++++
> ...vicePathLibMandatoryDevicePathProtocol.uni | 18 +
> ...iDevicePathLibOptionalDevicePathProtocol.c | 9 +-
> ...evicePathLibOptionalDevicePathProtocol.inf | 5 +-
> ...evicePathLibOptionalDevicePathProtocol.uni | 6 +-
> MdePkg/MdePkg.dsc | 3 +-
> 7 files changed, 582 insertions(+), 14 deletions(-)
> create mode 100644
>MdePkg/Library/UefiDevicePathLib/UefiDevicePathLibMandatoryDevicePath
>Protocol.c
> create mode 100644
>MdePkg/Library/UefiDevicePathLib/UefiDevicePathLibMandatoryDevicePath
>Protocol.inf
> create mode 100644
>MdePkg/Library/UefiDevicePathLib/UefiDevicePathLibMandatoryDevicePath
>Protocol.uni
>
>--
>2.21.0.windows.1
next prev parent reply other threads:[~2019-12-12 5:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 2:09 [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib instances Gao, Zhichao
2019-12-12 2:09 ` [PATCH V2 1/2] MdePkg/UefiDevicePathLib: Separate the device path lib Gao, Zhichao
2019-12-12 2:09 ` [PATCH V2 2/2] MdePkg/dsc: Add UefiDevicePathLibMandatoryDevicePathProtocol for build Gao, Zhichao
2019-12-12 5:05 ` Liming Gao [this message]
2019-12-12 5:28 ` [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib instances Gao, Zhichao
[not found] ` <15DF888FBF57C8A4.14754@groups.io>
2019-12-12 9:14 ` [edk2-devel] " Gao, Zhichao
2019-12-12 11:03 ` Liming Gao
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E564B61@SHSMSX104.ccr.corp.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