From: "Liming Gao" <liming.gao@intel.com>
To: "Jayanth.Raghuram@dell.com" <Jayanth.Raghuram@dell.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"leif.lindholm@linaro.org" <leif.lindholm@linaro.org>,
"afish@apple.com" <afish@apple.com>,
"lersek@redhat.com" <lersek@redhat.com>
Cc: "Wei.G.Liu@dell.com" <Wei.G.Liu@dell.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-devel] [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
Date: Thu, 29 Aug 2019 14:28:08 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E4DE421@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <f49e7ce938cf4c25aca609918a41a72d@ausx13mps324.AMER.DELL.COM>
[-- Attachment #1: Type: text/plain, Size: 6124 bytes --]
Jayanth:
Thanks for your update commit message. But, edk2 project doesn't use pull request.
You can send https://github.com/JayRaghuram/edk2 and say your patch is in this tree.
Leif gives the option. You need copy the patch content into the mail, then send this mail to devel@edk2.groups.io<mailto:devel@edk2.groups.io> for code review.
And, for this patch, I have some comments.
1. I have not given my reviewed-by. Please don't add it.
2. LocateHandleBuffer() service. UEFI spec defines that if there are no handles in the handle database
that match the search criteria, then EFI_NOT_FOUND is returned. So, when EFI_SUCCESS return,
don't need to check Handles and NoHandles. This change is not required.
3. GetSupportedTypes() service. UEFI spec doesn't define EFI_NOT_FOUND. So, when EFI_SUCCESS return,
InfoTypesBuffer may be NULL or InfoTypesBufferCount may be zero. I agree to add this checker.
Thanks
Liming
From: Jayanth.Raghuram@dell.com [mailto:Jayanth.Raghuram@dell.com]
Sent: Thursday, August 29, 2019 9:20 AM
To: Ni, Ray <ray.ni@intel.com>; Gao, Liming <liming.gao@intel.com>; Cetola, Stephano <stephano.cetola@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>; leif.lindholm@linaro.org; afish@apple.com; lersek@redhat.com
Cc: Wei.G.Liu@dell.com; devel@edk2.groups.io
Subject: RE: [edk2-devel] [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
Hi Liming,
Per your request, I have created an pull request as below:
https://github.com/tianocore/edk2/pull/147
MdePkg/DxeHstiLib: Added checks to improve error handling. #147
Open
JayRaghuram<https://github.com/JayRaghuram> wants to merge 1 commit into tianocore:master<https://github.com/tianocore/edk2> from JayRaghuram:master<https://github.com/JayRaghuram/edk2>
Regards
Jayanth Raghuram
DellEMC | Server Platform BIOS
office + 1 512 723 1470
From: Ni, Ray <ray.ni@intel.com<mailto:ray.ni@intel.com>>
Sent: Wednesday, August 28, 2019 12:33 PM
To: Gao, Liming; Cetola, Stephano; Kinney, Michael D; leif.lindholm@linaro.org<mailto:leif.lindholm@linaro.org>; Raghuram, Jayanth; 'Andrew Fish (afish@apple.com<mailto:afish@apple.com>)'; Laszlo Ersek
Cc: Liu, Wei G; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: [edk2-devel] [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
[EXTERNAL EMAIL]
Liming, Stephano and all stewards,
My understanding is the requirement of embedding patch into the mail body is due to a limitation in old system (01.org). That system couldn't support mail attachments.
With the existence of mail attachments capability in new groups.io system, can we accept such kind of patch submission? Or any side effect you see if allowing mail attachments?
Thanks,
Ray
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Liming Gao
Sent: Wednesday, August 28, 2019 12:59 AM
To: Jayanth.Raghuram@dell.com<mailto:Jayanth.Raghuram@dell.com>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Wei.G.Liu@dell.com<mailto:Wei.G.Liu@dell.com>
Subject: Re: [edk2-devel] [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
OK. So, you can't use git send-email to send this patch. Another way is to fork edk2 and create the branch to include this change.
Then, send the mail to let people review this patch in your branch.
And, for this patch, can you submit BZ https://bugzilla.tianocore.org/ first?
Then, update its commit message format based on this wiki.
https://github.com/tianocore/tianocore.github.io/wiki/Commit-Message-Format
Thanks
Liming
From: Jayanth.Raghuram@dell.com<mailto:Jayanth.Raghuram@dell.com> [mailto:Jayanth.Raghuram@dell.com]
Sent: Wednesday, August 28, 2019 2:30 AM
To: Gao, Liming <liming.gao@intel.com<mailto:liming.gao@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Wei.G.Liu@dell.com<mailto:Wei.G.Liu@dell.com>
Subject: RE: [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
Hi Liming,
I sent the review request based on the description in the links that you mentioned below.
I sent it in an Dell Email since I cannot use GIT SMTP to send email out from our servers.
Please let me know what is wrong and I can help rectify that.
Regards
Jayanth Raghuram
DellEMC | Server Platform BIOS
office + 1 512 723 1470
From: Gao, Liming <liming.gao@intel.com<mailto:liming.gao@intel.com>>
Sent: Monday, August 26, 2019 8:57 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Raghuram, Jayanth
Cc: Liu, Wei G
Subject: RE: [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
[EXTERNAL EMAIL]
Can you follow this process to send this patch again?
https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Development-Process
And, the commit message format is
https://github.com/tianocore/tianocore.github.io/wiki/Commit-Message-Format
Thanks
Liming
From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> [mailto:devel@edk2.groups.io] On Behalf Of Jayanth.Raghuram@dell.com<mailto:Jayanth.Raghuram@dell.com>
Sent: Tuesday, August 27, 2019 3:55 AM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Wei.G.Liu@dell.com<mailto:Wei.G.Liu@dell.com>
Subject: [edk2-devel] [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
Subject: [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
Added checks for return parameters of LocateHandleBuffer & GetSupportedTypes
function calls in InternalHstiFindAip to improve error handling. An issue was
observed on Dell Poweredge R740, where the Dell PERC H740P controller UEFI
driver returned InfoTypesBuffer = NULL, InfoTypesBufferCount = 0 and caused
an FreePool assert.
Signed-off-by: Jayanth Raghuram <Jayanth.Raghuram@Dell.com<mailto:Jayanth.Raghuram@Dell.com>>
Cc: Wei G Liu <Wei_G_Liu@Dell.com<mailto:Wei_G_Liu@Dell.com>>
Attached: 0001-MdePkg-DxeHstiLib-Added-checks-to-improve-error-hand.patch
Regards
Jayanth Raghuram
DellEMC | Server Platform BIOS
office + 1 512 723 1470
[-- Attachment #2: Type: text/html, Size: 28173 bytes --]
next prev parent reply other threads:[~2019-08-29 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 19:54 [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling Jayanth.Raghuram
2019-08-27 1:56 ` Liming Gao
2019-08-27 18:29 ` Jayanth.Raghuram
2019-08-28 7:59 ` Liming Gao
2019-08-28 17:33 ` [edk2-devel] " Ni, Ray
2019-08-29 1:19 ` Jayanth.Raghuram
2019-08-29 14:28 ` Liming Gao [this message]
2019-08-29 9:49 ` Leif Lindholm
2019-08-29 14:24 ` Laszlo Ersek
2019-08-29 17:02 ` Ni, Ray
2019-08-30 2:21 ` Nate DeSimone
2019-08-30 11:52 ` Laszlo Ersek
2019-08-30 11:49 ` Laszlo Ersek
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E4DE421@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