Re: [PATCH v2 RESEND] arm64: dts: nuvoton: ma35d1: add CAN nodes

Hi Arnd,

Thanks for the clarification.

Shan-Chun and I are still maintaining the MA35 platform.

I have reviewed this patch and it looks good to me.

Reviewed-by: Jacky Huang <ychuang3@nuvoton.com>

We agree that the current maintenance path for MA35 could be clearer.
We will work on making the MA35 maintenance flow more transparent.

Thanks for pointing this out.

Thanks,
Jacky

On Wed, Jul 8, 2026, at 10:24, Zi-Yu Chen wrote:

quoted

Add controller nodes for the four Bosch M_CAN blocks found on the
Nuvoton MA35D1 SoC.

Additionally, configure pinctrl and enable CAN1 and CAN3 on the
MA35D1 SOM board. Also, update the APLL frequency to 200MHz to ensure
the CAN controllers receive the required input clock for 50MHz operation.

Signed-off-by: Zi-Yu Chen <redacted>
---
Resend note:
  - resend with the complete Cc list; no patch changes

Hi,

I don't see anything wrong with the patch contents, but I think you still
have the wrong Cc list. You have sent the patch Cc: soc@lists.linux.dev,
which is where maintainers should send the patch when it is ready for
inclusion in the SoC tree, and you have sent it To Olof and me.
Olof retired as SoC tree maintainer a while ago, and I'm not going to
apply this because it should go through the Nuvoton tree maintained
by Jacky Huang and Shan-Chun Hung.

Please send future patches to the maintainers that are in charge of
applying the patches, without adding soc@lists.linux.dev yourself.
The maintainers will then forward it when they are happy with the
changes.

I just noticed that we have two conflicting maintainers entries
for ma35:

  - Jacky and Shan-Chun are listed for the ma35 SoC, but have
    not sent any updates after the initial merge in 2024 and
    don't currently have a git tree in linux-next

  - Andrew Jeffery and his team are listed for npcm with
    arch/arm64/boot/dts/nuvoton/ listed as one of the file
    locations, though that contains both ma35 and npcm.
    Andrew has the bmc tree in linux-next and has recently
    picked up patches for both npcm and ma35.

I see there is a lot of activity at the moment working on
ma35 drivers, so it would be good if the maintainers could
figure this out together and provide better guidance to
individual developers. I don't mind pulling from one
team or the other, but I would definitely prefer the MAINTAINERS
file to reflect the actual state here.

If Jacky and Shan-Chun are planning to do the merges going
forward, they should add their git tree to linux-next and
update the MAINTAINERS file to list the git URL.

       Arnd