From: Krzysztof Kozlowski <krzk@kernel.org>
To: Sebastian Kropatsch <seb-dev@web.de>,
Heiko Stuebner <heiko@sntech.de>,
linux-rockchip@lists.infradead.org
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: Add CM3588 NAS
Date: Mon, 27 May 2024 08:10:12 +0200 [thread overview]
Message-ID: <5f6a2469-5443-4edb-a13c-8b3bc5e4083c@kernel.org> (raw)
In-Reply-To: <20240526214625.8830-1-seb-dev@web.de>
On 26/05/2024 23:46, Sebastian Kropatsch wrote:
> Add devicetree binding for the FriendlyElec CM3588 NAS board.
>
> The CM3588 NAS by FriendlyElec pairs the CM3588 compute module, based on
> the Rockchip RK3588 SoC, with the CM3588 NAS Kit carrier board.
>
> Signed-off-by: Sebastian Kropatsch <seb-dev@web.de>
> ---
> Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-27 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-26 21:42 [PATCH 0/2] RK3588: FriendlyElec CM3588 NAS board support Sebastian Kropatsch
2024-05-26 21:46 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add CM3588 NAS Sebastian Kropatsch
2024-05-27 6:10 ` Krzysztof Kozlowski [this message]
2024-05-26 21:48 ` [PATCH 2/2] arm64: dts: rockchip: Add CM3588 NAS board Sebastian Kropatsch
2024-05-27 19:02 ` Jonas Karlman
2024-05-27 20:54 ` Heiko Stübner
2024-05-28 15:55 ` Sebastian Kropatsch
2024-05-29 7:57 ` Heiko Stübner
2024-05-29 15:53 ` Sebastian Kropatsch
2024-05-28 17:22 ` Sebastian Kropatsch
2024-05-29 0:10 ` Dragan Simic
2024-05-29 17:20 ` Sebastian Kropatsch
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=5f6a2469-5443-4edb-a13c-8b3bc5e4083c@kernel.org \
--to=krzk@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=robh@kernel.org \
--cc=seb-dev@web.de \
--cc=sebastian.reichel@collabora.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).