All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacky Huang <ychuang570808@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>, Zi-Yu Chen <zychennvt@gmail.com>
Cc: soc@lists.linux.dev, Jacky Huang <ychuang3@nuvoton.com>,
	schung@nuvoton.com, Rob Herring <robh@kernel.org>,
	krzk+dt@kernel.org, Conor Dooley <conor+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Jeffery <andrew@codeconstruct.com.au>
Subject: Re: [PATCH v2 RESEND] arm64: dts: nuvoton: ma35d1: add CAN nodes
Date: Mon, 13 Jul 2026 10:57:39 +0800	[thread overview]
Message-ID: <825a3a1b-8891-4172-afd6-8de6077fa129@gmail.com> (raw)
In-Reply-To: <5f2954e4-2e0c-40d0-b67f-933446c83cc1@app.fastmail.com>

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:
>> 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 <zychennvt@gmail.com>
>> ---
>> 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





  reply	other threads:[~2026-07-13  2:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-08  8:24 [PATCH v2 RESEND] arm64: dts: nuvoton: ma35d1: add CAN nodes Zi-Yu Chen
2026-07-10 14:16 ` Arnd Bergmann
2026-07-13  2:57   ` Jacky Huang [this message]
2026-08-04  5:13     ` Andrew Jeffery
2026-08-04  7:41       ` Arnd Bergmann

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=825a3a1b-8891-4172-afd6-8de6077fa129@gmail.com \
    --to=ychuang570808@gmail.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=arnd@arndb.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=schung@nuvoton.com \
    --cc=soc@lists.linux.dev \
    --cc=ychuang3@nuvoton.com \
    --cc=zychennvt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.