From: Conor Dooley <conor@kernel.org>
To: Yu-Chun Lin <eleanor.lin@realtek.com>
Cc: afaerber@suse.de, conor+dt@kernel.org, cy.huang@realtek.com,
devicetree@vger.kernel.org, james.tai@realtek.com,
krzk+dt@kernel.org, lee@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-realtek-soc@lists.infradead.org, robh@kernel.org,
stanley_chang@realtek.com
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: realtek: Add Kent Soc family compatibles
Date: Mon, 17 Nov 2025 14:36:23 +0000 [thread overview]
Message-ID: <20251117-platonic-settle-8c4f4b64aeb8@spud> (raw)
In-Reply-To: <20251117105542.14789-1-eleanor.lin@realtek.com>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
On Mon, Nov 17, 2025 at 06:55:42PM +0800, Yu-Chun Lin wrote:
> On Thu, Nov 13, 2025 at 08:30:07PM +0800, Yu-Chun Lin wrote:
> > > Define compatible strings for Realtek RTD1501s, RTD1861b and RTD1920s.
> > >
> > > Additionally, convert legacy DTS-style comments to YAML description
> > > properties, following the pattern from the ARM bindings conversion
> > > series [1].
> >
> > "Additionally" is often a sign that it should be in a different patch.
> > Acked-by: Conor Dooley <conor.dooley@microchip.com>
> > pw-bot: not-applicable
>
> Hi Conor,
>
> I'm planning to split the changes into two separate patches:
>
> 1. One patch to convert realtek.yaml to match the DTS-style comments,
> following the pattern from the ARM bindings conversion series.
> 2. Another patch to define the compatible strings for Realtek RTD1501s,
> RTD1861b, and RTD1920s.
>
> Could you confirm if both patches should include your Acked-by tag, or is
> it only applicable to one of them?
I acked it to go together, because I didn't think it was worth a
resubmission for that alone. You can keep the ack I think, I'll take a
look regardless.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-17 14:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 12:30 [PATCH v2 0/3] arm64: dts: Add support for Kent SoC family Yu-Chun Lin
2025-11-13 12:30 ` [PATCH v2 1/3] dt-bindings: arm: realtek: Add Kent Soc family compatibles Yu-Chun Lin
2025-11-13 19:28 ` Conor Dooley
2025-11-17 10:55 ` Yu-Chun Lin
2025-11-17 14:36 ` Conor Dooley [this message]
2025-11-13 12:30 ` [PATCH v2 2/3] dt-bindings: mfd: Add Realtek MISC system controller Yu-Chun Lin
2025-11-13 19:31 ` Conor Dooley
2025-11-13 19:36 ` Krzysztof Kozlowski
2025-11-17 11:03 ` Yu-Chun Lin [林祐君]
2025-11-17 11:10 ` Krzysztof Kozlowski
2025-11-17 12:41 ` Yu-Chun Lin [林祐君]
2025-11-17 13:31 ` Krzysztof Kozlowski
2025-11-19 6:46 ` Yu-Chun Lin [林祐君]
2025-11-13 12:30 ` [PATCH v2 3/3] arm64: dts: realtek: Add Kent SoC and EVB device trees Yu-Chun Lin
2025-11-13 19:39 ` Krzysztof Kozlowski
2025-11-13 19:50 ` Krzysztof Kozlowski
2025-11-17 12:43 ` Yu-Chun Lin [林祐君]
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=20251117-platonic-settle-8c4f4b64aeb8@spud \
--to=conor@kernel.org \
--cc=afaerber@suse.de \
--cc=conor+dt@kernel.org \
--cc=cy.huang@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=eleanor.lin@realtek.com \
--cc=james.tai@realtek.com \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-realtek-soc@lists.infradead.org \
--cc=robh@kernel.org \
--cc=stanley_chang@realtek.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;
as well as URLs for NNTP newsgroup(s).