public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
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: [edk2-devel] [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib instances
Date: Thu, 12 Dec 2019 11:03:28 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E564EF8@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <3CE959C139B4C44DBEA1810E3AA6F9000B8936F5@SHSMSX101.ccr.corp.intel.com>

Thanks for your test. Reviewed-by: Liming Gao <liming.gao@intel.com>

> -----Original Message-----
> From: Gao, Zhichao <zhichao.gao@intel.com>
> Sent: Thursday, December 12, 2019 5:15 PM
> To: devel@edk2.groups.io; Gao, Zhichao <zhichao.gao@intel.com>; Gao, Liming <liming.gao@intel.com>
> Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Vitaly Cheptsov <vit9696@protonmail.com>
> Subject: RE: [edk2-devel] [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib instances
> 
> I have ported a test case from SCT to test the interfaces in UefiDevicePathLibMandatoryDevicePathProtocol.c and
> UefiDevicePathLibOptionalDevicePathProtocol.c only.
> And I do the test on Ovmf environment for two configuration: one is include DevicePathDxe, and the other is not.
> Optional one lib test cases would always passed.
> Mandatory one lib test case would passed with Ovmf with DevicePathDxe, and ASSERT with the other.
> 
> The test result is expected.
> Tested-by: Zhichao Gao <zhichao.gao@intel.com>
> 
> Thanks,
> Zhichao
> 
> > -----Original Message-----
> > From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> > Gao, Zhichao
> > Sent: Thursday, December 12, 2019 1:29 PM
> > To: Gao, Liming <liming.gao@intel.com>; devel@edk2.groups.io
> > Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Vitaly Cheptsov
> > <vit9696@protonmail.com>
> > Subject: Re: [edk2-devel] [PATCH V2 0/2] MdePkg/UefiDevicePathLib:
> > Separate the lib instances
> >
> > Actually I didn't do the functionality test of Mandatory one, only do the build
> > test and logic check. It is part of the Optional one. I assume the optional one
> > is working fine. Then there would be no problem with Mandatory one.
> > I would write a test for both of them to make sure they are both fine.
> >
> > Thanks,
> > Zhichao
> >
> > > -----Original Message-----
> > > From: Gao, Liming
> > > Sent: Thursday, December 12, 2019 1:05 PM
> > > To: Gao, Zhichao <zhichao.gao@intel.com>; 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
> > >
> > > 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/UefiDevicePathLibMandatoryDevicePa
> > > th
> > > >Protocol.c
> > > > create mode 100644
> > >
> > >MdePkg/Library/UefiDevicePathLib/UefiDevicePathLibMandatoryDevicePa
> > > th
> > > >Protocol.inf
> > > > create mode 100644
> > >
> > >MdePkg/Library/UefiDevicePathLib/UefiDevicePathLibMandatoryDevicePa
> > > th
> > > >Protocol.uni
> > > >
> > > >--
> > > >2.21.0.windows.1
> >
> >
> > 


      reply	other threads:[~2019-12-12 11:03 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 ` [PATCH V2 0/2] MdePkg/UefiDevicePathLib: Separate the lib instances Liming Gao
2019-12-12  5:28   ` Gao, Zhichao
     [not found]   ` <15DF888FBF57C8A4.14754@groups.io>
2019-12-12  9:14     ` [edk2-devel] " Gao, Zhichao
2019-12-12 11:03       ` Liming Gao [this message]

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E564EF8@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