From: "Arnd Bergmann" <arnd@arndb.de>
To: "Andrew Jeffery" <andrew@codeconstruct.com.au>,
"Jacky Huang" <ychuang570808@gmail.com>,
"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
Subject: Re: [PATCH v2 RESEND] arm64: dts: nuvoton: ma35d1: add CAN nodes
Date: Tue, 04 Aug 2026 09:41:39 +0200 [thread overview]
Message-ID: <fa1d3251-817d-4095-8fc0-dbee0f9cbafc@app.fastmail.com> (raw)
In-Reply-To: <6da6d2fa5111e479aeefd62da70974601acccb96.camel@codeconstruct.com.au>
On Tue, Aug 4, 2026, at 07:13, Andrew Jeffery wrote:
> On Mon, 2026-07-13 at 10:57 +0800, Jacky Huang wrote:
>> 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.
>
> I discussed this with Jacky off-list. Going forward I'll take MA35
> patches with R-b tags from Jacky and Zi-Yu through the BMC tree to keep
> things simple.
>
> I'll pick up v2 for the next merge window if there are no other issues
> with it.
Sounds good, thanks!
Arnd
prev parent reply other threads:[~2026-08-04 7:42 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
2026-08-04 5:13 ` Andrew Jeffery
2026-08-04 7:41 ` Arnd Bergmann [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=fa1d3251-817d-4095-8fc0-dbee0f9cbafc@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrew@codeconstruct.com.au \
--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=ychuang570808@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox