From: "Nickle Wang via groups.io" <nicklew=nvidia.com@groups.io>
To: Mike Maslenkin <mike.maslenkin@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "abner.chang@amd.com" <abner.chang@amd.com>,
"igork@ami.com" <igork@ami.com>
Subject: Re: [edk2-devel] [PATCH 0/5] RedfishClientPkg: fix issues with local variables.
Date: Mon, 28 Aug 2023 09:03:19 +0000 [thread overview]
Message-ID: <MW4PR12MB70312B91F521E28DC4D2EE27D9E0A@MW4PR12MB7031.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230827105640.94731-1-mike.maslenkin@gmail.com>
Hi Mike,
> I didn't find any codyng-style issues in uncrustify output.
I fetch your branch and run uncrustify tool to fix error in vs code editor. I push the fix to your branch at this commit for your reference: https://github.com/ghbaccount/edk2-redfish-client/commit/f22209f7bd5946168326a3197006d92856247d35 The uncrustify check on PR is now passed successfully. My commit breaks patch check as expected, please incorporate my changes with yours and do a force push to this PR again.
For the way of fixing uncrustify error, I am using the instructions here: https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-Code-Formatting#recommended-usage-visual-studio-vs-code-plugin
Thanks,
Nickle
> -----Original Message-----
> From: Mike Maslenkin <mike.maslenkin@gmail.com>
> Sent: Sunday, August 27, 2023 6:57 PM
> To: devel@edk2.groups.io
> Cc: abner.chang@amd.com; Nickle Wang <nicklew@nvidia.com>;
> igork@ami.com; Mike Maslenkin <mike.maslenkin@gmail.com>
> Subject: [PATCH 0/5] RedfishClientPkg: fix issues with local variables.
>
> External email: Use caution opening links or attachments
>
>
> This patchset contains fixes that resolve crashes while working with uninitialized
> variables and a number of fixes for of leaked memory.
> Note: looks like uncrustify check is broken at tianocore/edk2-redfish-client repo,
> the corresponding PR failed:
> https://github.co/
> m%2Ftianocore%2Fedk2-redfish-
> client%2Fpull%2F46&data=05%7C01%7Cnicklew%40nvidia.com%7C7cf336153fb
> f4e2e821008dba6ec62e0%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0
> %7C638287306436105158%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAw
> MDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C
> &sdata=VUxJA017msZzRYd%2FAxi0KeZvLi2s0QI6uKgHsOuDdws%3D&reserved=0
>
> I didn't find any codyng-style issues in uncrustify output.
>
> Cc: Abner Chang <abner.chang@amd.com>
> Cc: Nickle Wang <nicklew@nvidia.com>
> Cc: Igor Kulchytskyy <igork@ami.com>
> Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#108053): https://edk2.groups.io/g/devel/message/108053
Mute This Topic: https://groups.io/mt/100988470/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-08-28 9:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 10:56 [edk2-devel] [PATCH 0/5] RedfishClientPkg: fix issues with local variables Mike Maslenkin
2023-08-27 10:56 ` [edk2-devel] [PATCH 1/5] RedfishClientPkg: fix crash on access to uninialized list variable Mike Maslenkin
2023-08-27 10:56 ` [edk2-devel] [PATCH 2/5] RedfishClientPkg: fix access to uninitialized variable Mike Maslenkin
2023-08-27 10:56 ` [edk2-devel] [PATCH 3/5] RedfishClientPkg: fix leak of allocated Etag data Mike Maslenkin
2023-08-27 10:56 ` [edk2-devel] [PATCH 4/5] RedfishClientPkg: fix memory leak during EFI variables write Mike Maslenkin
2023-08-27 10:56 ` [edk2-devel] [PATCH 5/5] RedfishClientPkg: fix misprints in Readme.md Mike Maslenkin
2023-08-28 9:03 ` Nickle Wang via groups.io [this message]
2023-08-28 23:18 ` [edk2-devel] [PATCH 0/5] RedfishClientPkg: fix issues with local variables Mike Maslenkin
2023-08-29 7:45 ` Nickle Wang via groups.io
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=MW4PR12MB70312B91F521E28DC4D2EE27D9E0A@MW4PR12MB7031.namprd12.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