From: "Rob Herring (Arm)" <robh@kernel.org>
To: Heiko Stuebner <heiko@sntech.de>
Cc: conor+dt@kernel.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-rockchip@lists.infradead.org, uwe@kleine-koenig.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 4/5] dt-bindings: arm: rockchip: add TS133 to RK356x-based QNAP NAS devices
Date: Tue, 6 Jan 2026 12:30:57 -0600 [thread overview]
Message-ID: <176772425740.2513273.11038899818156080578.robh@kernel.org> (raw)
In-Reply-To: <20260104191448.2693309-5-heiko@sntech.de>
On Sun, 04 Jan 2026 20:14:47 +0100, Heiko Stuebner wrote:
> QNAP builds a number of variants of the RK356x-based NAS design.
>
> Add the 1-bay TS133 variant.
>
> This one is a tiny bit special as it is based around the RK3566 variant
> of the mostly similar RK3566/RK3568 SoCs.
>
> Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> ---
> .../devicetree/bindings/arm/rockchip.yaml | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-01-06 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 19:14 [PATCH 0/5] Support for QNAP TS133 variant Heiko Stuebner
2026-01-04 19:14 ` [PATCH 1/5] arm64: dts: rockchip: Move SoC include to individual QNAP TSx33 boards Heiko Stuebner
2026-01-04 19:14 ` [PATCH 2/5] arm64: dts: rockchip: Fix the common combophy + SATA on QNAP TSx33 devices Heiko Stuebner
2026-01-04 19:14 ` [PATCH 3/5] arm64: dts: rockchip: Move copy-key to TSx33 board files Heiko Stuebner
2026-01-04 19:14 ` [PATCH 4/5] dt-bindings: arm: rockchip: add TS133 to RK356x-based QNAP NAS devices Heiko Stuebner
2026-01-06 18:30 ` Rob Herring (Arm) [this message]
2026-01-04 19:14 ` [PATCH 5/5] arm64: dts: rockchip: Add TS133 variant of the QNAP NAS series Heiko Stuebner
2026-01-13 14:04 ` [PATCH 0/5] Support for QNAP TS133 variant Heiko Stuebner
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=176772425740.2513273.11038899818156080578.robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=uwe@kleine-koenig.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®