mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <lukas.bulwahn@gmail.com>, <Daire.McNamara@microchip.com>,
	<linux-riscv@lists.infradead.org>, <wsa@kernel.org>,
	<arnd@arndb.de>
Cc: <kernel-janitors@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: rectify entry for RISC-V/MICROCHIP POLARFIRE SOC SUPPORT
Date: Thu, 11 Aug 2022 07:14:15 +0000	[thread overview]
Message-ID: <47742925-2d0d-7313-f811-aa17e35ce81a@microchip.com> (raw)
In-Reply-To: <20220811070506.12252-1-lukas.bulwahn@gmail.com>

On 11/08/2022 08:05, Lukas Bulwahn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Commit 3cbd67384677 ("MAINTAINERS: add the Polarfire SoC's i2c driver")
> adds the file entry for drivers/i2c/busses/i2c-microchip-core.c, but the
> file is actually named drivers/i2c/busses/i2c-microchip-corei2c.c.
> 
> Repair this file reference in RISC-V/MICROCHIP POLARFIRE SOC SUPPORT.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Conor, please ack.

FFS... Silly mistake from me there, keep getting caught out by
the maintainers entries when I do an inter-version rename.
Is there something I can add to my build scripts, other than the
get_maintainer selftest to catch these?
Thanks Lukas.

Acked-by: Conor Dooley <conor.dooley@microchip.com>

> 
> Arnd, please pick this minor non-urgent clean-up patch.
> 
>   MAINTAINERS | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 9203efedea1e..797fde7e1821 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17544,7 +17544,7 @@ F:      Documentation/devicetree/bindings/usb/microchip,mpfs-musb.yaml
>   F:     arch/riscv/boot/dts/microchip/
>   F:     drivers/char/hw_random/mpfs-rng.c
>   F:     drivers/clk/microchip/clk-mpfs.c
> -F:     drivers/i2c/busses/i2c-microchip-core.c
> +F:     drivers/i2c/busses/i2c-microchip-corei2c.c
>   F:     drivers/mailbox/mailbox-mpfs.c
>   F:     drivers/pci/controller/pcie-microchip-host.c
>   F:     drivers/rtc/rtc-mpfs.c
> --
> 2.17.1
> 


  reply	other threads:[~2022-08-11  7:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11  7:05 Lukas Bulwahn
2022-08-11  7:14 ` Conor.Dooley [this message]
2022-08-11  7:32   ` Lukas Bulwahn
2022-08-11  8:01     ` Conor.Dooley
2022-08-11  8:43       ` Conor.Dooley
2022-08-11 10:47 ` Wolfram Sang

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-all 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=47742925-2d0d-7313-f811-aa17e35ce81a@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Daire.McNamara@microchip.com \
    --cc=arnd@arndb.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=wsa@kernel.org \
    /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

all inboxes | Powered by JetHome®