Hi Jacky and Arnd On Sun, 19 Mar 2023 at 14:01, Jacky Huang <ychuang570808@xxxxxxxxx> 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@xxxxxxxxxxx> > >> > >> Add entry for Nuvton ma35d1 maintainer and files > >> > >> Signed-off-by: Jacky Huang <ychuang3@xxxxxxxxxxx> > >> --- > >> +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
