From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Sergiu Moga <sergiu.moga@microchip.com>,
<gregkh@linuxfoundation.org>, <krzk@kernel.org>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"kernel test robot" <lkp@intel.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Claudiu Beznea <Claudiu.Beznea@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] MAINTAINERS: Solve warning regarding inexistent atmel-usart binding
Date: Fri, 23 Sep 2022 15:19:17 +0200 [thread overview]
Message-ID: <53b7639a-174f-7a49-10a2-60eaa838278a@microchip.com> (raw)
In-Reply-To: <20220923113415.90236-1-sergiu.moga@microchip.com>
On 23/09/2022 at 13:34, Sergiu Moga wrote:
> After the conversion to json-schema, what was previously known as
> `Documentation/devicetree/bindings/mfd/atmel-usart.txt`
> has been moved to another bindings directory and renamed to
> `Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml`.
> Thus, make `MAINTAINERS` reflect this change.
>
> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
> Reported-by: kernel test robot <lkp@intel.com>
Acked-by: Nicolas Ferre <nicolas.ferre@microchip.com>
Thanks for having fixed that Sergiu. Regards,
Nicolas
> ---
> MAINTAINERS | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d30f26e07cd3..7308dfba6f0e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13292,7 +13292,7 @@ F: include/dt-bindings/dma/at91.h
> MICROCHIP AT91 SERIAL DRIVER
> M: Richard Genoud <richard.genoud@gmail.com>
> S: Maintained
> -F: Documentation/devicetree/bindings/mfd/atmel-usart.txt
> +F: Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
> F: drivers/tty/serial/atmel_serial.c
> F: drivers/tty/serial/atmel_serial.h
>
> @@ -13300,7 +13300,7 @@ MICROCHIP AT91 USART MFD DRIVER
> M: Radu Pirea <radu_nicolae.pirea@upb.ro>
> L: linux-kernel@vger.kernel.org
> S: Supported
> -F: Documentation/devicetree/bindings/mfd/atmel-usart.txt
> +F: Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
> F: drivers/mfd/at91-usart.c
> F: include/dt-bindings/mfd/at91-usart.h
>
> @@ -13308,7 +13308,7 @@ MICROCHIP AT91 USART SPI DRIVER
> M: Radu Pirea <radu_nicolae.pirea@upb.ro>
> L: linux-spi@vger.kernel.org
> S: Supported
> -F: Documentation/devicetree/bindings/mfd/atmel-usart.txt
> +F: Documentation/devicetree/bindings/serial/atmel,at91-usart.yaml
> F: drivers/spi/spi-at91-usart.c
>
> MICROCHIP AUDIO ASOC DRIVERS
--
Nicolas Ferre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
parent reply other threads:[~2022-09-23 13:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220923113415.90236-1-sergiu.moga@microchip.com>]
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=53b7639a-174f-7a49-10a2-60eaa838278a@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=sergiu.moga@microchip.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;
as well as URLs for NNTP newsgroup(s).