From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yu-Chun Lin <eleanor15x@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
james.tai@realtek.com, soc@lists.linux.dev
Cc: afaerber@suse.de, arnd@arndb.de,
linux-arm-kernel@lists.infradead.org,
linux-realtek-soc@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
cy.huang@realtek.com, stanley_chang@realtek.com,
eleanor.lin@realtek.com,
Conor Dooley <conor.dooley@microchip.com>
Subject: Re: [PATCH RESEND v3 1/2] dt-bindings: arm: realtek: Add Kent Soc family compatibles
Date: Wed, 28 Jan 2026 19:35:53 +0100 [thread overview]
Message-ID: <a09292b2-0c40-497f-8270-b089e499f97d@kernel.org> (raw)
In-Reply-To: <20260127071530.25426-2-eleanor15x@gmail.com>
On 27/01/2026 08:14, Yu-Chun Lin wrote:
> From: Yu-Chun Lin <eleanor.lin@realtek.com>
>
> 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].
>
> [1] https://lore.kernel.org/lkml/20200622125527.24207-2-afaerber@suse.de/
>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> Signed-off-by: Yu-Chun Lin <eleanor.lin@realtek.com>
> ---
Arnd, FWIW:
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-28 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 7:13 [PATCH RESEND v3 0/2] arm64: dts: Add support for Kent SoC family Yu-Chun Lin
2026-01-27 7:14 ` [PATCH RESEND v3 1/2] dt-bindings: arm: realtek: Add Kent Soc family compatibles Yu-Chun Lin
2026-01-28 18:35 ` Krzysztof Kozlowski [this message]
2026-01-27 7:14 ` [PATCH RESEND v3 2/2] arm64: dts: realtek: Add Kent SoC and EVB device trees Yu-Chun Lin
2026-01-28 18:41 ` Krzysztof Kozlowski
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=a09292b2-0c40-497f-8270-b089e499f97d@kernel.org \
--to=krzk@kernel.org \
--cc=afaerber@suse.de \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=cy.huang@realtek.com \
--cc=devicetree@vger.kernel.org \
--cc=eleanor.lin@realtek.com \
--cc=eleanor15x@gmail.com \
--cc=james.tai@realtek.com \
--cc=krzk+dt@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=soc@lists.linux.dev \
--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