public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Li, Yi" <yi1.li@intel.com>
To: "Clark-williams, Zachary" <zachary.clark-williams@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH] NetworkPkg: Correct the length of EAP Identity when in ASCII format
Date: Mon, 26 Jun 2023 08:36:22 +0000	[thread overview]
Message-ID: <SJ1PR11MB62272FB4CBE0334275DBD4B8C526A@SJ1PR11MB6227.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO6PR11MB5601593E988ED8EE4FC69B16C922A@CO6PR11MB5601.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]

Hi Zack,

Please check V3 patch, thanks for review.

Regards,
Yi

From: Clark-williams, Zachary <zachary.clark-williams@intel.com>
Sent: Friday, June 23, 2023 6:26 AM
To: devel@edk2.groups.io; Li, Yi1 <yi1.li@intel.com>; Clark-williams, Zachary <zachary.clark-williams@intel.com>
Subject: RE: [edk2-devel] [PATCH] NetworkPkg: Correct the length of EAP Identity when in ASCII format

Hey Yi,

I agree with the flow you have in the PR link and removing the extra protocol locate.

My only comment is to align your comments with the commenting style of the file.
Instead of /**/, use // for both single and multi-line comments.
Example included in the comments on the PR.

Thanks,
Zack


From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Li, Yi
Sent: Monday, June 19, 2023 9:49 PM
To: Clark-williams; Clark-williams, Zachary <zachary.clark-williams@intel.com<mailto:zachary.clark-williams@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH] NetworkPkg: Correct the length of EAP Identity when in ASCII format

Hi Zachary,

Thanks for review.
The protocol has changes since ADL from PlatSapmle to an advanced feature and the Protocol has shifted into EDK2, so the protocol name needs to be updated:
+  Status = gBS->LocateProtocol (&gWiFiProfileSyncProtocolGuid, NULL, (VOID **) &WiFiProfileSyncProtocol);
    Status = gBS->LocateProtocol (&gEdkiiWiFiProfileSyncProtocolGuid, NULL, (VOID **)&WiFiProfileSyncProtocol);

The locate protocol status check is enough and we do not need to add the NULL check too, we can remove that to keep it lighter.
+    if (!EFI_ERROR (Status) && WiFiProfileSyncProtocol != NULL) {
Agree with those changes, please check latest V2 patch or this PR: https://github.com/tianocore/edk2/pull/4561
Can we clean up the second locate protocol and bring the Identity allocate above the protocol check, and bring the two conditions for EapIdentity copied to Identity into the added protocol check condition.
Here is a view of what I am thinking for consolidation.
We need to get the Identity size before AllocateZeroPool(), not feasible here IMO.


[-- Attachment #2: Type: text/html, Size: 6874 bytes --]

  reply	other threads:[~2023-06-26  8:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  6:29 [PATCH] NetworkPkg: Correct the length of EAP Identity when in ASCII format Li, Yi
2023-06-16 19:07 ` [edk2-devel] " Clark-williams, Zachary
2023-06-20  4:49   ` Li, Yi
2023-06-22 22:26     ` Clark-williams, Zachary
2023-06-26  8:36       ` Li, Yi [this message]
2023-06-27 18:07         ` Clark-williams, Zachary
     [not found] <1765AF83686A77A3.7352@groups.io>
2023-06-12  1:52 ` Li, Yi

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=SJ1PR11MB62272FB4CBE0334275DBD4B8C526A@SJ1PR11MB6227.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