From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jagan Teki <jagan@amarulasolutions.com>,
Heiko Stuebner <heiko@sntech.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
FUKAUMI Naoki <naoki@radxa.com>
Subject: Re: [PATCH v2 1/4] arm64: dts: rockchip: Fix compatible for Radxa CM3
Date: Mon, 23 Jan 2023 08:59:51 +0100 [thread overview]
Message-ID: <110befb9-090e-54e4-b669-ec81a89580e0@linaro.org> (raw)
In-Reply-To: <20230123071654.73139-1-jagan@amarulasolutions.com>
On 23/01/2023 08:16, Jagan Teki wrote:
> The compatible string "radxa,radxa-cm3" referring the product name
> as "Radxa Radxa CM3" but the actual product name is "Radxa CM3".
>
> Fix the compatible strings.
>
> Fixes: 24a28d3eb07d ("dt-bindings: arm: rockchip: Add Radxa Compute
> Module 3")
> Fixes: 7469ab529bca ("arm64: dts: rockchip: Add rk3566 based Radxa
> Compute Module 3")
> Fixes: 096ebfb74b19 ("arm64: dts: rockchip: Add Radxa Compute Module
> 3 IO board")
> Suggested-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
Don't wrap the tags.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-01-23 7:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 7:16 [PATCH v2 1/4] arm64: dts: rockchip: Fix compatible for Radxa CM3 Jagan Teki
2023-01-23 7:16 ` [PATCH v2 2/4] arm64: dts: rockchip: Add missing CM3i fallback compatible for Radxa E25 Jagan Teki
2023-01-23 7:16 ` [PATCH v2 3/4] arm64: dts: rockchip: Drop unneeded model for Radxa CM3i Jagan Teki
2023-01-23 7:16 ` [PATCH v2 4/4] arm64: dts: rockchip: Correct the model name for Radxa E25 Jagan Teki
2023-01-23 7:59 ` Krzysztof Kozlowski [this message]
2023-01-29 13:39 ` [PATCH v2 1/4] arm64: dts: rockchip: Fix compatible for Radxa CM3 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=110befb9-090e-54e4-b669-ec81a89580e0@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jagan@amarulasolutions.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).