From: Chi-Wen Weng <cwweng.linux@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cwweng@nuvoton.com
Subject: Re: [PATCH 1/2] dt-bindings: spi: nuvoton,ma35d1-spi: Add Nuvoton MA35D1 SPI controller
Date: Thu, 24 Sep 2026 09:26:47 +0800 [thread overview]
Message-ID: <cee8c7b8-88d8-42d9-b425-31adb499ad40@gmail.com> (raw)
In-Reply-To: <arO_P5imHln19iV-@sirena.co.uk>
Mark Brown 於 2026/9/23 下午 07:59 寫道:
> On Wed, Sep 23, 2026 at 12:19:25PM +0800, Chi-Wen Weng wrote:
>> From: Chi-Wen Weng <cwweng@nuvoton.com>
>>
>> Add a Devicetree binding for the SPI controller found in the
>> Nuvoton MA35D1 SoC.
>
> Please submit patches using subject lines reflecting the style for the
> subsystem, this makes it easier for people to identify relevant patches.
> Look at what existing commits in the area you're changing are doing and
> make sure your subject lines visually resemble what they're doing.
> There's no need to resubmit to fix this alone.
Hi Mark,
Thanks for the review.
I will update the binding patch subject in the next revision to follow
the SPI subsystem convention, for example:
spi: dt-bindings: nuvoton,ma35d1-spi: Add Nuvoton MA35D1 SPI controller
I won't resend the series for this change alone.
Thanks,
Chi-Wen
next prev parent reply other threads:[~2026-09-24 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 4:19 [PATCH 0/2] spi: ma35d1: Add Nuvoton MA35D1 SPI controller support Chi-Wen Weng
2026-09-23 4:19 ` [PATCH 1/2] dt-bindings: spi: nuvoton,ma35d1-spi: Add Nuvoton MA35D1 SPI controller Chi-Wen Weng
2026-09-23 11:59 ` Mark Brown
2026-09-24 1:26 ` Chi-Wen Weng [this message]
2026-09-23 12:35 ` Krzysztof Kozlowski
2026-09-24 3:03 ` Chi-Wen Weng
2026-09-23 4:19 ` [PATCH 2/2] spi: ma35d1: Add Nuvoton MA35D1 SPI controller support Chi-Wen Weng
2026-09-23 12:25 ` Mark Brown
2026-09-24 2:14 ` Chi-Wen Weng
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=cee8c7b8-88d8-42d9-b425-31adb499ad40@gmail.com \
--to=cwweng.linux@gmail.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cwweng@nuvoton.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@kernel.org \
/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
all inboxes | Powered by JetHome®