From: "Pete Batard" <pete@akeo.ie>
To: Jeremy Linton <jeremy.linton@arm.com>, devel@edk2.groups.io
Cc: Leif Lindholm <leif@nuviainc.com>,
Andrei Warkentin <awarkentin@vmware.com>,
Ard Biesheuvel <ard.biesheuvel@arm.com>,
Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: Re: [PATCH v3 5/5] Platform/RaspberryPi: Trivial whitespace cleanup
Date: Mon, 31 Aug 2020 14:17:45 +0100 [thread overview]
Message-ID: <229d8727-b26b-51ac-7b7e-e183607834c2@akeo.ie> (raw)
In-Reply-To: <20200828220215.101919-6-jeremy.linton@arm.com>
Thanks for this.
On 2020.08.28 23:02, Jeremy Linton wrote:
> Pete's review pointed out some whitespace issues in the
> context of a previous patch. Since there are a number of
> similar errors in the file lets fix them separately.
>
> Cc: Leif Lindholm <leif@nuviainc.com>
> Cc: Pete Batard <pete@akeo.ie>
> Cc: Andrei Warkentin <awarkentin@vmware.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> ---
> Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c | 26 +++++++++++-----------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c b/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
> index d58cbbdfe7..2712194d2b 100644
> --- a/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
> +++ b/Platform/RaspberryPi/Drivers/ConfigDxe/ConfigDxe.c
> @@ -209,9 +209,9 @@ SetupVariables (
> }
>
>
>
> Size = sizeof (UINT32);
>
> - Status = gRT->GetVariable(L"CustomCpuClock",
>
> - &gConfigDxeFormSetGuid,
>
> - NULL, &Size, &Var32);
>
> + Status = gRT->GetVariable (L"CustomCpuClock",
>
> + &gConfigDxeFormSetGuid,
>
> + NULL, &Size, &Var32);
>
> if (EFI_ERROR (Status)) {
>
> Status = PcdSet32S (PcdCustomCpuClock, PcdGet32 (PcdCustomCpuClock));
>
> ASSERT_EFI_ERROR (Status);
>
> @@ -256,9 +256,9 @@ SetupVariables (
> PcdSet32 (PcdFanOnGpio, PcdGet32 (PcdFanOnGpio));
>
> }
>
>
>
> - Size = sizeof(AssetTagVar);
>
> + Size = sizeof (AssetTagVar);
>
>
>
> - Status = gRT->GetVariable(L"AssetTag",
>
> + Status = gRT->GetVariable (L"AssetTag",
>
> &gConfigDxeFormSetGuid,
>
> NULL, &Size, AssetTagVar);
>
>
>
> @@ -267,7 +267,7 @@ SetupVariables (
> L"AssetTag",
>
> &gConfigDxeFormSetGuid,
>
> EFI_VARIABLE_NON_VOLATILE | EFI_VARIABLE_BOOTSERVICE_ACCESS | EFI_VARIABLE_RUNTIME_ACCESS,
>
> - sizeof(AssetTagVar),
>
> + sizeof (AssetTagVar),
>
> AssetTagVar
>
> );
>
> }
>
> @@ -433,9 +433,9 @@ ApplyVariables (
> * spaces. SystemMemorySizeBelow4GB tracks the maximum memory below 4GB
>
> * line, factoring in the limit imposed by the SoC register range.
>
> */
>
> - SystemMemorySizeBelow4GB = MIN(SystemMemorySize, 4UL * SIZE_1GB);
>
> - SystemMemorySizeBelow4GB = MIN(SystemMemorySizeBelow4GB, BCM2836_SOC_REGISTERS);
>
> - SystemMemorySizeBelow4GB = MIN(SystemMemorySizeBelow4GB, BCM2711_SOC_REGISTERS);
>
> + SystemMemorySizeBelow4GB = MIN (SystemMemorySize, 4UL * SIZE_1GB);
>
> + SystemMemorySizeBelow4GB = MIN (SystemMemorySizeBelow4GB, BCM2836_SOC_REGISTERS);
>
> + SystemMemorySizeBelow4GB = MIN (SystemMemorySizeBelow4GB, BCM2711_SOC_REGISTERS);
>
>
>
> ASSERT (SystemMemorySizeBelow4GB > 3UL * SIZE_1GB);
>
>
>
> @@ -528,14 +528,14 @@ ApplyVariables (
> /*
>
> * SD card pins go to Arasan.
>
> */
>
> - MmioWrite32((GPIO_BASE_ADDRESS + 0xD0),
>
> - MmioRead32(GPIO_BASE_ADDRESS + 0xD0) | 0x2);
>
> + MmioWrite32 ((GPIO_BASE_ADDRESS + 0xD0),
>
> + MmioRead32 (GPIO_BASE_ADDRESS + 0xD0) | 0x2);
>
> } else {
>
> /*
>
> * SD card pins back to eMMC2.
>
> */
>
> - MmioWrite32((GPIO_BASE_ADDRESS + 0xD0),
>
> - MmioRead32(GPIO_BASE_ADDRESS + 0xD0) & ~0x2);
>
> + MmioWrite32 ((GPIO_BASE_ADDRESS + 0xD0),
>
> + MmioRead32 (GPIO_BASE_ADDRESS + 0xD0) & ~0x2);
>
> /*
>
> * WiFi back to Arasan.
>
> */
>
Reviewed-by: Pete Batard <pete@akeo.ie>
prev parent reply other threads:[~2020-08-31 13:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 22:02 [PATCH v3 0/5] Platform/RasberryPi: Thermal zone Jeremy Linton
2020-08-28 22:02 ` [PATCH v3 1/5] Platform/RaspberryPi4: Add a basic thermal zone Jeremy Linton
2020-08-31 13:15 ` Pete Batard
2020-08-31 15:13 ` Jeremy Linton
2020-08-31 15:33 ` Ard Biesheuvel
2020-08-31 15:49 ` Jeremy Linton
2020-08-28 22:02 ` [PATCH v3 2/5] Platform/RaspberryPi: Monitor ACPI Table installs Jeremy Linton
2020-08-31 13:17 ` Pete Batard
2020-08-28 22:02 ` [PATCH v3 3/5] Platform/RaspberryPi: Add entry for user fan control Jeremy Linton
2020-08-31 13:17 ` Pete Batard
2020-08-28 22:02 ` [PATCH v3 4/5] Platform/RaspberryPi4: Create ACPI fan object Jeremy Linton
2020-08-31 13:17 ` Pete Batard
2020-08-28 22:02 ` [PATCH v3 5/5] Platform/RaspberryPi: Trivial whitespace cleanup Jeremy Linton
2020-08-31 13:17 ` Pete Batard [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=229d8727-b26b-51ac-7b7e-e183607834c2@akeo.ie \
--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