From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>
Cc: linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: rectify file pattern in MICROCHIP OTPC DRIVER
Date: Tue, 14 Jun 2022 11:27:13 -0700 [thread overview]
Message-ID: <06ae64cc-80e0-9290-5d9f-1a37184ed900@linaro.org> (raw)
In-Reply-To: <20220607064220.9296-1-lukas.bulwahn@gmail.com>
On 06/06/2022 23:42, Lukas Bulwahn wrote:
> Commit 6b291610dd57 ("nvmem: microchip-otpc: add support") adds the
> Microchip otpc driver and a corresponding MAINTAINERS section, but slips
> in a slightly wrong file pattern.
>
> Hence, ./scripts/get_maintainer.pl --self-test=patterns complains about a
> broken reference.
>
> Rectify this file pattern in MICROCHIP OTPC DRIVER.
>
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
Applied thanks,
--srini
> Claudiu, please ack.
>
> Srinivas, please pick this minor non-urgent patch in your -next tree on
> top of the commit above. Thanks.
>
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 572f50739fb2..288393564abc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13119,7 +13119,7 @@ L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> S: Supported
> F: Documentation/devicetree/bindings/nvmem/microchip,sama7g5-otpc.yaml
> F: drivers/nvmem/microchip-otpc.c
> -F: dt-bindings/nvmem/microchip,sama7g5-otpc.h
> +F: include/dt-bindings/nvmem/microchip,sama7g5-otpc.h
>
> MICROCHIP PWM DRIVER
> M: Claudiu Beznea <claudiu.beznea@microchip.com>
prev parent reply other threads:[~2022-06-14 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 6:42 Lukas Bulwahn
2022-06-07 8:18 ` Claudiu.Beznea
2022-06-14 18:27 ` Srinivas Kandagatla [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-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=06ae64cc-80e0-9290-5d9f-1a37184ed900@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=claudiu.beznea@microchip.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
/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®