From: Conor Dooley <conor@kernel.org>
To: devicetree@vger.kernel.org, Conor Dooley <conor@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: Thu, 27 Jun 2024 17:28:50 +0100 [thread overview]
Message-ID: <20240627-scrap-negation-8e123d3b20fb@spud> (raw)
In-Reply-To: <20240626-platter-scarcity-d503fda8a2fd@spud>
From: Conor Dooley <conor.dooley@microchip.com>
On Wed, 26 Jun 2024 16:54:16 +0100, Conor Dooley wrote:
> 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.
>
>
Applied to riscv-cache-for-next, thanks!
[2/2] MAINTAINERS: add cache binding directory to cache driver entry
https://git.kernel.org/conor/c/4ca47d8bcca0
Thanks,
Conor.
prev parent reply other threads:[~2024-06-27 16:29 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 ` [PATCH 1/2] MAINTAINERS: add microchip soc binding directory to microchip soc " Conor Dooley
2024-06-27 7:35 ` Nicolas Ferre
2024-06-27 7:38 ` Krzysztof Kozlowski
2024-06-27 16:28 ` Conor Dooley [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=20240627-scrap-negation-8e123d3b20fb@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