From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Gregory Clement <gregory.clement@bootlin.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Lubomir Rintel <lkundrak@v3.sk>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: marvell: move MMP boards to common marvell directory
Date: Fri, 1 Dec 2023 15:21:05 +0100 [thread overview]
Message-ID: <a44b7bb2-34ac-45ab-84c6-630d604f1bcf@linaro.org> (raw)
In-Reply-To: <1e25e2f4-e4b9-4219-a9c2-cb6230a62549@lunn.ch>
On 01/12/2023 14:51, Andrew Lunn wrote:
> On Fri, Dec 01, 2023 at 02:23:06PM +0100, Krzysztof Kozlowski wrote:
>> Marvell board bindings are spread over arm/marvell/ and arm/mrvl/
>> directories. Move MMP board bindings from the latter to the former, to
>> keep all of them together.
>
> Hi Krzysztof
>
> Did you test get_maintainers.pl? MMP has a different maintainer to
> many of the other Marvell SoCs. We want emails going to the correct
> Maintainers, and ideally not spamming the others.
The old binding was not referenced in MAINTAINERS, at least I could not
find it.
My change does not affect status quo - orphaned files.
OTOH, some entries like Orion list specific files. Others like Marvell
list entire directory, which is their mistake in the first place.
There is a mess in this approach, but the mess exists before my patch.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-01 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 13:23 Krzysztof Kozlowski
2023-12-01 13:51 ` Andrew Lunn
2023-12-01 14:21 ` Krzysztof Kozlowski [this message]
2023-12-01 14:34 ` Andrew Lunn
2023-12-01 14:38 ` Krzysztof Kozlowski
2023-12-01 16:17 ` Andrew Lunn
2023-12-07 13:57 ` 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=a44b7bb2-34ac-45ab-84c6-630d604f1bcf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@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®