From: Marek Vasut <marex@denx.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linux-arm-kernel@lists.infradead.org
Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
Fabio Estevam <festevam@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
NXP Linux Team <linux-imx@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add entry for DHCOM i.MX8M Plus SoMs and boards
Date: Wed, 18 Jan 2023 13:35:23 +0100 [thread overview]
Message-ID: <13b341ba-92d1-0989-5d7c-a9df080ca56b@denx.de> (raw)
In-Reply-To: <e3b73baf-b36b-17c0-f414-bbf2dd746411@linaro.org>
On 1/18/23 12:37, Krzysztof Kozlowski wrote:
> On 17/01/2023 23:38, Marek Vasut wrote:
>> Add maintainers entry for DH electronics DHCOM i.MX8M Plus
>> based SoMs and boards.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> ---
>> Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>
>> Cc: Fabio Estevam <festevam@gmail.com>
>> Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
>> Cc: Marek Vasut <marex@denx.de>
>> Cc: NXP Linux Team <linux-imx@nxp.com>
>> Cc: Peng Fan <peng.fan@nxp.com>
>> Cc: Pengutronix Kernel Team <kernel@pengutronix.de>
>> Cc: Rob Herring <robh+dt@kernel.org>
>> Cc: Sascha Hauer <s.hauer@pengutronix.de>
>> Cc: Shawn Guo <shawnguo@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> To: linux-arm-kernel@lists.infradead.org
>> ---
>> MAINTAINERS | 6 ++++++
>> 1 file changed, 6 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index d0a36e45aa4be..e9be585d507e9 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -5968,6 +5968,12 @@ S: Maintained
>> F: arch/arm/boot/dts/imx6*-dhcom-*
>> F: arch/arm/boot/dts/imx6*-dhcor-*
>>
>> +DH ELECTRONICS IMX8M PLUS DHCOM BOARD SUPPORT
>> +M: Marek Vasut <marex@denx.de>
>> +L: kernel@dh-electronics.com
>> +S: Maintained
>> +F: arch/arm64/boot/dts/freescale/imx8mp*-dhcom-*
>
> We do not keep maintainer per board. The idea was to use in-board
> emails, but the patch doing that was not accepted. But regardless -
> entries per board in maintainers is crazy amount of new entries. Way too
> many.
What would you propose I should do here to get a valid entry for this
machine ?
next prev parent reply other threads:[~2023-01-18 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 22:38 [PATCH] MAINTAINERS: Add entry for DHCOM i.MX8M Plus SoMs and boards Marek Vasut
2023-01-18 11:37 ` Krzysztof Kozlowski
2023-01-18 12:35 ` Marek Vasut [this message]
2023-01-18 12:38 ` Krzysztof Kozlowski
2023-01-18 12:47 ` Marek Vasut
2023-01-18 13:10 ` Krzysztof Kozlowski
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=13b341ba-92d1-0989-5d7c-a9df080ca56b@denx.de \
--to=marex@denx.de \
--cc=cniedermaier@dh-electronics.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).