From: <Conor.Dooley@microchip.com>
To: <lukas.bulwahn@gmail.com>, <wsa@kernel.org>
Cc: <linux-i2c@vger.kernel.org>, <peter@korsgaard.com>,
<andrew@lunn.ch>, <kernel-janitors@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] MAINTAINERS: Rectify entry for OPENCORES I2C BUS DRIVER
Date: Fri, 10 Jun 2022 10:59:21 +0000 [thread overview]
Message-ID: <98ebfad6-3480-5065-fc50-74c8fe85f322@microchip.com> (raw)
In-Reply-To: <20220610105154.2358-1-lukas.bulwahn@gmail.com>
On 10/06/2022 11:51, Lukas Bulwahn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> Commit 8ad69f490516 ("dt-bindings: i2c: convert ocores binding to yaml")
> converts i2c-ocores.txt to opencores,i2c-ocores.yaml, but then adjust its
> reference in MAINTAINERS to a slightly wrong new filename.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
>
> Repair this file reference in OPENCORES I2C BUS DRIVER.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> Conor, please ack.
Ahh crap, changed the filename from feedback and forgot to
make the corresponding change.. Thanks for fixing my mess!
Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Wolfram, please pick this minor non-urgent clean-up patch for your -next tree.
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index fc5b74ad0141..02e91ac4ee04 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14920,7 +14920,7 @@ M: Peter Korsgaard <peter@korsgaard.com>
> M: Andrew Lunn <andrew@lunn.ch>
> L: linux-i2c@vger.kernel.org
> S: Maintained
> -F: Documentation/devicetree/bindings/i2c/i2c-ocores.yaml
> +F: Documentation/devicetree/bindings/i2c/opencores,i2c-ocores.yaml
> F: Documentation/i2c/busses/i2c-ocores.rst
> F: drivers/i2c/busses/i2c-ocores.c
> F: include/linux/platform_data/i2c-ocores.h
> --
> 2.17.1
>
next prev parent reply other threads:[~2022-06-10 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 10:51 Lukas Bulwahn
2022-06-10 10:59 ` Conor.Dooley [this message]
2022-06-10 11:18 ` Peter Korsgaard
2022-06-13 14:42 ` 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=98ebfad6-3480-5065-fc50-74c8fe85f322@microchip.com \
--to=conor.dooley@microchip.com \
--cc=andrew@lunn.ch \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=peter@korsgaard.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®