From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"mikuback@linux.microsoft.com" <mikuback@linux.microsoft.com>,
"Ni, Ray" <ray.ni@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 2/8] FatPkg/FatPei: Remove extraneous debug message argument
Date: Thu, 8 Sep 2022 16:45:32 +0000 [thread overview]
Message-ID: <CO1PR11MB4929391B29636AC79EDD1B8AD2409@CO1PR11MB4929.namprd11.prod.outlook.com> (raw)
In-Reply-To: <ed0f2b90-77f7-b69f-389c-5f66cb3b0fe0@linux.microsoft.com>
Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Mike
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Michael Kubacki
> Sent: Thursday, September 8, 2022 9:28 AM
> To: Ni, Ray <ray.ni@intel.com>; devel@edk2.groups.io
> Subject: Re: [edk2-devel] [PATCH v3 2/8] FatPkg/FatPei: Remove extraneous debug message argument
>
> Still need this review.
>
> Patch has been on list for over a month and changes one line of code.
>
> On 9/6/2022 11:05 PM, Michael Kubacki wrote:
> > Hello Ray,
> >
> > Can you please review this patch?
> >
> > FatPkg is the only package missing a review on the series.
> >
> > Thanks,
> > Michael
> >
> > On 9/2/2022 6:22 PM, Michael Kubacki wrote:
> >> From: Michael Kubacki <michael.kubacki@microsoft.com>
> >>
> >> This debug macro should take one argument based on the number of
> >> print specifiers defined. However, two arguments are given.
> >>
> >> It looks like the code may have been refactored such that the
> >> second argument was moved to a new print and this argument was
> >> not removed. In any case, it should not be there now.
> >>
> >> Cc: Ray Ni <ray.ni@intel.com>
> >> Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
> >> ---
> >> FatPkg/FatPei/Gpt.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/FatPkg/FatPei/Gpt.c b/FatPkg/FatPei/Gpt.c
> >> index 0a1a25ceeff1..9e17ce88086f 100644
> >> --- a/FatPkg/FatPei/Gpt.c
> >> +++ b/FatPkg/FatPei/Gpt.c
> >> @@ -361,7 +361,7 @@ PartitionCheckGptEntryArray (
> >> PrivateData->BlockDeviceCount++;
> >> - DEBUG ((DEBUG_INFO, "Find GPT Partition [0x%lx",
> >> PartitionEntryBuffer[Index].StartingLBA, BlockDevPtr->LastBlock));
> >> + DEBUG ((DEBUG_INFO, "Find GPT Partition [0x%lx",
> >> PartitionEntryBuffer[Index].StartingLBA));
> >> DEBUG ((DEBUG_INFO, ", 0x%lx]\n", BlockDevPtr->LastBlock));
> >> DEBUG ((DEBUG_INFO, " BlockSize %x\n",
> >> BlockDevPtr->BlockSize));
> >> }
> >
> >
> >
> >
>
>
>
>
prev parent reply other threads:[~2022-09-08 16:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 22:21 [PATCH v3 0/8] Fix imbalanced debug macros Michael Kubacki
2022-09-02 22:21 ` [PATCH v3 1/8] ArmPlatformPkg/NorFlashDxe: Remove unused debug print specifier Michael Kubacki
2022-09-02 22:22 ` [PATCH v3 2/8] FatPkg/FatPei: Remove extraneous debug message argument Michael Kubacki
2022-09-02 22:22 ` [PATCH v3 3/8] MdeModulePkg: Fix imbalanced debug macros Michael Kubacki
2022-09-02 22:22 ` [PATCH v3 4/8] RedfishPkg/RedfishRestExDxe: Remove extra debug macro argument Michael Kubacki
2022-09-05 7:20 ` [edk2-devel] " nickle
2022-09-02 22:22 ` [PATCH v3 5/8] SecurityPkg/SmmTcg2PhysicalPresenceLib: Add missing debug print specifier Michael Kubacki
2022-09-02 22:22 ` [PATCH v3 6/8] DynamicTablesPkg/AcpiPpttLibArm: Fix debug macro arguments Michael Kubacki
2022-09-02 22:22 ` [PATCH v3 7/8] NetworkPkg/TcpDxe: " Michael Kubacki
2022-09-02 22:22 ` [PATCH v3 8/8] OvmfPkg/LegacyBootManagerLib: " Michael Kubacki
2022-09-05 6:24 ` Gerd Hoffmann
2022-09-05 7:53 ` Ard Biesheuvel
[not found] ` <17112B50E738A0A8.6506@groups.io>
2022-09-07 3:05 ` [edk2-devel] [PATCH v3 2/8] FatPkg/FatPei: Remove extraneous debug message argument Michael Kubacki
[not found] ` <17127514CA861B0C.26635@groups.io>
2022-09-08 16:28 ` Michael Kubacki
2022-09-08 16:45 ` Michael D Kinney [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=CO1PR11MB4929391B29636AC79EDD1B8AD2409@CO1PR11MB4929.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