[15/15] MAINTAINERS: Add entry for NUVOTON MA35

Message ID 20230315072902.9298-16-ychuang570808@gmail.com
State New
Headers
Series Introduce Nuvoton ma35d1 SoC |

Commit Message

Jacky Huang March 15, 2023, 7:29 a.m. UTC
  From: Jacky Huang <ychuang3@nuvoton.com>

Add entry for Nuvton ma35d1 maintainer and files

Signed-off-by: Jacky Huang <ychuang3@nuvoton.com>
---
 MAINTAINERS | 12 ++++++++++++
 1 file changed, 12 insertions(+)
  

Comments

Arnd Bergmann March 16, 2023, 2:38 p.m. UTC | #1
On Wed, Mar 15, 2023, at 08:29, Jacky Huang wrote:
> From: Jacky Huang <ychuang3@nuvoton.com>
>
> Add entry for Nuvton ma35d1 maintainer and files
>
> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com>
> ---

> +F:	Documentation/devicetree/bindings/*/*nuvoton*
> +F:	arch/arm64/boot/dts/nuvoton/

This clashes with the existing entry for NPCM, so
contributors can easily get confused about where
to send their dts patches.

I don't have a good solution here, but maybe you can
discuss this with the npcm maintainers (added to Cc)
to see how they would like to handle this.

For me, the easiest way would be to have a single
maintainer send me all the patches for both ma35d1
and npcm, but that may not be practical for you.

> +F:	drivers/*/*/*ma35d1*
> +F:	drivers/*/*ma35d1*
> +F:	include/dt-bindings/*/*ma35d1*
> +F:	include/linux/mfd/ma35d1-sys.h

I would replace these with a single line

K:    ma35d1

that should have the same effect.

     Arnd
  
Jacky Huang March 19, 2023, 12:01 p.m. UTC | #2
Dear Arnd,


Thanks for your advice.


On 2023/3/16 下午 10:38, Arnd Bergmann wrote:
> On Wed, Mar 15, 2023, at 08:29, Jacky Huang wrote:
>> From: Jacky Huang <ychuang3@nuvoton.com>
>>
>> Add entry for Nuvton ma35d1 maintainer and files
>>
>> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com>
>> ---
>> +F:	Documentation/devicetree/bindings/*/*nuvoton*
>> +F:	arch/arm64/boot/dts/nuvoton/
> This clashes with the existing entry for NPCM, so
> contributors can easily get confused about where
> to send their dts patches.
>
> I don't have a good solution here, but maybe you can
> discuss this with the npcm maintainers (added to Cc)
> to see how they would like to handle this.
>
> For me, the easiest way would be to have a single
> maintainer send me all the patches for both ma35d1
> and npcm, but that may not be practical for you.


All I can do so far is, once we receive a patch for npcm,

forward it to the maintainers of npcm, and the npcm side

does the same.

And I would like to modify it as

+F:	arch/arm64/boot/dts/nuvoton/*ma35*

>> +F:	drivers/*/*/*ma35d1*
>> +F:	drivers/*/*ma35d1*
>> +F:	include/dt-bindings/*/*ma35d1*
>> +F:	include/linux/mfd/ma35d1-sys.h
> I would replace these with a single line
>
> K:    ma35d1
>
> that should have the same effect.
>
>       Arnd


It's fine. I will use K: instead. Thank you.


Best regards,

Jacky Huang
  
Tomer Maimon March 19, 2023, 12:36 p.m. UTC | #3
Hi Jacky and Arnd

On Sun, 19 Mar 2023 at 14:01, Jacky Huang <ychuang570808@gmail.com> wrote:
>
> Dear Arnd,
>
>
> Thanks for your advice.
>
>
> On 2023/3/16 下午 10:38, Arnd Bergmann wrote:
> > On Wed, Mar 15, 2023, at 08:29, Jacky Huang wrote:
> >> From: Jacky Huang <ychuang3@nuvoton.com>
> >>
> >> Add entry for Nuvton ma35d1 maintainer and files
> >>
> >> Signed-off-by: Jacky Huang <ychuang3@nuvoton.com>
> >> ---
> >> +F:  Documentation/devicetree/bindings/*/*nuvoton*
> >> +F:  arch/arm64/boot/dts/nuvoton/
> > This clashes with the existing entry for NPCM, so
> > contributors can easily get confused about where
> > to send their dts patches.
> >
> > I don't have a good solution here, but maybe you can
> > discuss this with the npcm maintainers (added to Cc)
> > to see how they would like to handle this.
> >
> > For me, the easiest way would be to have a single
> > maintainer send me all the patches for both ma35d1
> > and npcm, but that may not be practical for you.
>
>
> All I can do so far is, once we receive a patch for npcm,
>
> forward it to the maintainers of npcm, and the npcm side
We can forward ma35 DTS emails to you as well.
>
> does the same.
>
> And I would like to modify it as
>
> +F:     arch/arm64/boot/dts/nuvoton/*ma35*
About modify
F: arch/arm64/boot/dts/nuvoton/
to
F: arch/arm64/boot/dts/nuvoton/*npcm*
We can't guarantee that our customers will use npcm in the dts files name.
>
> >> +F:  drivers/*/*/*ma35d1*
> >> +F:  drivers/*/*ma35d1*
> >> +F:  include/dt-bindings/*/*ma35d1*
> >> +F:  include/linux/mfd/ma35d1-sys.h
> > I would replace these with a single line
> >
> > K:    ma35d1
> >
> > that should have the same effect.
> >
> >       Arnd
>
>
> It's fine. I will use K: instead. Thank you.
>
>
> Best regards,
>
> Jacky Huang
>
>

Thanks,

Tomer
  

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index ec57c42ed544..b42d5c052863 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2535,6 +2535,18 @@  F:	arch/arm/mach-npcm/wpcm450.c
 F:	drivers/*/*/*wpcm*
 F:	drivers/*/*wpcm*
 
+ARM/NUVOTON MA35 ARCHITECTURE
+M:	Jacky Huang <ychuang3@nuvoton.com>
+M:	Shan-Chun Hung <schung@nuvoton.com>
+L:	linux-arm-kernel@lists.infradead.org (moderated for non-subscribers)
+S:	Supported
+F:	Documentation/devicetree/bindings/*/*nuvoton*
+F:	arch/arm64/boot/dts/nuvoton/
+F:	drivers/*/*/*ma35d1*
+F:	drivers/*/*ma35d1*
+F:	include/dt-bindings/*/*ma35d1*
+F:	include/linux/mfd/ma35d1-sys.h
+
 ARM/NXP S32G ARCHITECTURE
 M:	Chester Lin <clin@suse.com>
 R:	Andreas Färber <afaerber@suse.de>