linux-kernel - Re: [PATCH v2 1/3] dt-bindings: arm: realtek: Add Kent Soc family compatibles

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251117-platonic-settle-8c4f4b64aeb8@spud>
Date: Mon, 17 Nov 2025 14:36:23 +0000
From: Conor Dooley <conor@...nel.org>
To: Yu-Chun Lin <eleanor.lin@...ltek.com>
Cc: afaerber@...e.de, conor+dt@...nel.org, cy.huang@...ltek.com,
	devicetree@...r.kernel.org, james.tai@...ltek.com,
	krzk+dt@...nel.org, lee@...nel.org,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-realtek-soc@...ts.infradead.org, robh@...nel.org,
	stanley_chang@...ltek.com
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: realtek: Add Kent Soc family
 compatibles

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@...rochip.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.

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)