2023-06-07 19:29:30

by Biju Das

[permalink] [raw]
Subject: RE: [PATCH] PCI: rcar: user proper naming for R-Car

Hi Wolfram,

> Subject: [PATCH] PCI: rcar: user proper naming for R-Car

Typo %s/user/use/ on patch subject??

Cheers,
Biju

>
> Neither RCar, nor Rcar, but R-Car.
>
> Signed-off-by: Wolfram Sang <[email protected]>
> ---
> drivers/pci/controller/pcie-rcar-host.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/pci/controller/pcie-rcar-host.c
> b/drivers/pci/controller/pcie-rcar-host.c
> index e80e56b2a842..f4dac8ff97cb 100644
> --- a/drivers/pci/controller/pcie-rcar-host.c
> +++ b/drivers/pci/controller/pcie-rcar-host.c
> @@ -684,7 +684,7 @@ static void rcar_compose_msi_msg(struct irq_data
> *data, struct msi_msg *msg) }
>
> static struct irq_chip rcar_msi_bottom_chip = {
> - .name = "Rcar MSI",
> + .name = "R-Car MSI",
> .irq_ack = rcar_msi_irq_ack,
> .irq_mask = rcar_msi_irq_mask,
> .irq_unmask = rcar_msi_irq_unmask,
> @@ -813,7 +813,7 @@ static int rcar_pcie_enable_msi(struct rcar_pcie_host
> *host)
>
> /*
> * Setup MSI data target using RC base address address, which
> - * is guaranteed to be in the low 32bit range on any RCar HW.
> + * is guaranteed to be in the low 32bit range on any R-Car HW.
> */
> rcar_pci_write_reg(pcie, lower_32_bits(res.start) | MSIFE,
> PCIEMSIALR);
> rcar_pci_write_reg(pcie, upper_32_bits(res.start), PCIEMSIAUR);
> --
> 2.35.1



2023-06-07 21:26:28

by Wolfram Sang

[permalink] [raw]
Subject: Re: [PATCH] PCI: rcar: user proper naming for R-Car


> Typo %s/user/use/ on patch subject??

Yes, you are right. Will send v2


Attachments:
(No filename) (80.00 B)
signature.asc (849.00 B)
Download all attachments