From: Conor Dooley <conor@kernel.org>
To: devicetree@vger.kernel.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>
Subject: Re: [PATCH 1/2] MAINTAINERS: add microchip soc binding directory to microchip soc driver entry
Date: Wed, 26 Jun 2024 17:10:47 +0100 [thread overview]
Message-ID: <20240626-daybreak-psychic-b563872acb48@spud> (raw)
In-Reply-To: <20240626-platter-scarcity-d503fda8a2fd@spud>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
On Wed, Jun 26, 2024 at 04:54:16PM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> I noticed that there's technically not an explicit maintainer for this
> directory, even if the files currently in it are covered by either the
> Mircochip FPGA or AT91 entries. Add it to the entry covering the
> corresponding driver directory.
>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> CC: Rob Herring <robh@kernel.org>
> CC: Krzysztof Kozlowski <krzk+dt@kernel.org>
> CC: Conor Dooley <conor+dt@kernel.org>
> CC: devicetree@vger.kernel.org
> CC: Nicolas Ferre <nicolas.ferre@microchip.com>
> CC: Alexandre Belloni <alexandre.belloni@bootlin.com>
> CC: Claudiu Beznea <claudiu.beznea@tuxon.dev>
> CC: Lars Povlsen <lars.povlsen@microchip.com>
> CC: Steen Hegelund <Steen.Hegelund@microchip.com>
> CC: Daniel Machon <daniel.machon@microchip.com>
Huh, I somehow didn't save my updated commit message. The long list of
microchip people here is because it was a move of a sparx5 binding to
this directly that caused me to notice the lack of explicit coverage of
the directory.
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e2d8fdda1737..c74fd2b70532 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14975,6 +14975,7 @@ MICROCHIP SOC DRIVERS
> M: Conor Dooley <conor@kernel.org>
> S: Supported
> T: git https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/
> +F: Documentation/devicetree/bindings/soc/microchip/
> F: drivers/soc/microchip/
>
> MICROCHIP SPI DRIVER
> --
> 2.43.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2024-06-26 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 15:54 [PATCH 1/2] MAINTAINERS: add microchip soc binding directory to microchip soc driver entry Conor Dooley
2024-06-26 15:54 ` [PATCH 2/2] MAINTAINERS: add cache binding directory to cache " Conor Dooley
2024-06-27 7:38 ` Krzysztof Kozlowski
2024-06-26 16:10 ` Conor Dooley [this message]
2024-06-27 7:35 ` [PATCH 1/2] MAINTAINERS: add microchip soc binding directory to microchip soc " Nicolas Ferre
2024-06-27 7:38 ` Krzysztof Kozlowski
2024-06-27 16:28 ` Conor Dooley
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=20240626-daybreak-psychic-b563872acb48@spud \
--to=conor@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh@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