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: Thu, 7 Dec 2023 14:57:52 +0100 [thread overview]
Message-ID: <526bfe1e-7f6a-4402-80d6-2c97a1e3198e@linaro.org> (raw)
In-Reply-To: <9c50d09e-98a0-416f-b779-9cf39d1a94b5@lunn.ch>
On 01/12/2023 17:17, Andrew Lunn wrote:
> On Fri, Dec 01, 2023 at 03:38:36PM +0100, Krzysztof Kozlowski wrote:
>> On 01/12/2023 15:34, Andrew Lunn wrote:
>>> On Fri, Dec 01, 2023 at 03:21:05PM +0100, Krzysztof Kozlowski wrote:
>>>> 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.
>>>
>>> I think these moved files will now match:
>>>
>>> ARM/Marvell Kirkwood and Armada 370, 375, 38x, 39x, XP, 3700, 7K/8K, CN9130 SOC support
>>> M: Andrew Lunn <andrew@lunn.ch>
>>> M: Gregory Clement <gregory.clement@bootlin.com>
>>> M: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
>>> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
>>> S: Maintained
>>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/gclement/mvebu.git
>>> F: Documentation/devicetree/bindings/arm/marvell/
>>>
>>> But these files are not Gregory or my problem.
>>
>> Yeah, that's what I meant by listing entire directory.
>>
>>>
>>> If they were orphaned before, i would prefer they are either orphaned
>>> after the move, or associated to the correct maintainer. Being
>>> associated to the wrong maintainers is worse than having no
>>> maintainers at all.
>>
>> I can add this to existing maintainers entry. Which one? I see only two
>> ARM/Marvell.
>
> MMP SUPPORT
> R: Lubomir Rintel <lkundrak@v3.sk>
> L: linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
> S: Odd Fixes
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/lkundrak/linux-mmp.git
> F: arch/arm/boot/dts/marvell/mmp*
> F: arch/arm/mach-mmp/
> F: include/linux/soc/mmp/
>
> But you also need to modify the ARM/Marvell Kirkwood and ... so that
> it excludes these MMP files.
Let's make it then in subdirectory? There are like 20 items from
Marvell/Kirkwood, so I imagine all apply to it. At least currently they
are applying.
Best regards,
Krzysztof
prev parent reply other threads:[~2023-12-07 13:58 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
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 [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=526bfe1e-7f6a-4402-80d6-2c97a1e3198e@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®