From: "Gao, Liming" <liming.gao@intel.com>
To: Ashish Singhal <ashishsingha@nvidia.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Fu, Siyuan" <siyuan.fu@intel.com>, "Wu, Jiaxin" <jiaxin.wu@intel.com>
Subject: Re: [PATCH v4 0/2] Provide UEFILib functions for protocol uninstallation
Date: Thu, 10 Jan 2019 15:22:36 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3AF073@SHSMSX152.ccr.corp.intel.com> (raw)
In-Reply-To: <BYAPR12MB27437D72FB69071E22DE8F58BA840@BYAPR12MB2743.namprd12.prod.outlook.com>
Ashish:
The MdePkg change is good to me. Reviewed-by: Liming Gao <liming.gao@intel.com>
Please help submit another BZ to update UefiDriver to uninstall protocol when failure with new APIs.
If Siyuan/Jiaxin has no other comments, I will help push this patch set.
Thanks
Liming
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ashish Singhal
> Sent: Thursday, January 10, 2019 9:19 AM
> To: Kinney, Michael D <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
> Cc: Fu, Siyuan <siyuan.fu@intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>; Gao, Liming <liming.gao@intel.com>
> Subject: Re: [edk2] [PATCH v4 0/2] Provide UEFILib functions for protocol uninstallation
>
> Thanks Mike. Hope to see the patches merged soon. Please let me know if you want me to file the BZ.
>
> Hi Liming,
>
> Please let me know if you need me to take care of anything in the patch before you push it.
>
> Hi Siyuan/Jiaxin,
>
> I think you reviewed the changes in PATCH v2 which is same as in PATCH v4. Please let me know if you have any issues with this going in.
>
> Thanks
> Ashish
>
> -----Original Message-----
> From: Kinney, Michael D <michael.d.kinney@intel.com>
> Sent: Wednesday, January 9, 2019 5:56 PM
> To: Ashish Singhal <ashishsingha@nvidia.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
> Cc: Gao, Liming <liming.gao@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>; Wu, Jiaxin <jiaxin.wu@intel.com>
> Subject: RE: [PATCH v4 0/2] Provide UEFILib functions for protocol uninstallation
>
> Hi Ashish,
>
> This V4 version of the patch produces the expected size results for platform and driver builds.
>
> There are some very minor issues with some extra carriage returns, but those can be handled by Liming when the patch series is
> committed.
>
> I may be good to have an additional BZ to use these new APIs from all UEFI Driver Model drivers that have failure paths in their entry
> point or support the unload feature.
> Those updates can be done later.
>
> Thanks,
>
> Mike
>
> > -----Original Message-----
> > From: Ashish Singhal [mailto:ashishsingha@nvidia.com]
> > Sent: Wednesday, January 9, 2019 12:59 PM
> > To: edk2-devel@lists.01.org
> > Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Gao, Liming
> > <liming.gao@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>; Wu, Jiaxin
> > <jiaxin.wu@intel.com>; Ashish Singhal <ashishsingha@nvidia.com>
> > Subject: [PATCH v4 0/2] Provide UEFILib functions for protocol
> > uninstallation
> >
> > An issue was seen in IScsiDxe in NetworkPkg where driver cleanup after
> > initialization failure was not done right. Bug 1428 was filed in this
> > regard.
> > As per discussions with Mike, it was also discussed that having
> > UEFILib provide protocol uninstallation abstraction would help to
> > avoid these issues in the future. Bug 1429 was found to track this.
> > These 2 patches
> > take care of this.
> >
> >
> > Ashish Singhal (2):
> > MdePkg/UefiLib: Abstract driver model protocol uninstallation
> > NetworkPkg/IScsiDxe: Use UEFILib APIs to uninstall protocols.
> >
> > MdePkg/Include/Library/UefiLib.h | 103 ++++
> > MdePkg/Library/UefiLib/UefiDriverModel.c | 972
> > ++++++++++++++++++++++++++++++-
> > NetworkPkg/IScsiDxe/IScsiDriver.c | 31 +-
> > 3 files changed, 1085 insertions(+), 21 deletions(-)
> >
> > --
> > 2.7.4
>
> -----------------------------------------------------------------------------------
> This email message is for the sole use of the intended recipient(s) and may contain
> confidential information. Any unauthorized review, use, disclosure or distribution
> is prohibited. If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
> -----------------------------------------------------------------------------------
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2019-01-10 15:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 20:58 [PATCH v4 0/2] Provide UEFILib functions for protocol uninstallation Ashish Singhal
2019-01-09 20:58 ` [PATCH v4 1/2] MdePkg/UefiLib: Abstract driver model " Ashish Singhal
2019-01-09 20:58 ` [PATCH v4 2/2] NetworkPkg/IScsiDxe: Use UEFILib APIs to uninstall protocols Ashish Singhal
2019-01-10 0:55 ` [PATCH v4 0/2] Provide UEFILib functions for protocol uninstallation Kinney, Michael D
2019-01-10 1:18 ` Ashish Singhal
2019-01-10 15:22 ` Gao, Liming [this message]
2019-01-10 15:33 ` Ashish Singhal
2019-01-10 15:39 ` Gao, Liming
2019-01-10 15:40 ` Ashish Singhal
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E3AF073@SHSMSX152.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