From: Dragan Simic <dsimic@manjaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Chukun Pan <amadeus@jmu.edu.cn>, Heiko Stuebner <heiko@sntech.de>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: rockchip: add Radxa ROCK 3C
Date: Sun, 28 Apr 2024 23:41:24 +0200 [thread overview]
Message-ID: <f4baaff6fe20bba48cddb356df6e531a@manjaro.org> (raw)
In-Reply-To: <d6004beb-2e7d-4f26-a202-0c5baabd4023@kernel.org>
Hello Krzysztof,
On 2024-04-28 18:37, Krzysztof Kozlowski wrote:
> On 28/04/2024 14:36, Chukun Pan wrote:
>> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml
>> b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> index 1bbbaf81134b..e04c213a0dee 100644
>> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
>> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> @@ -799,6 +799,11 @@ properties:
>> - const: radxa,rock3a
>> - const: rockchip,rk3568
>>
>> + - description: Radxa ROCK 3C
>
> There was some big renaming of these boards. I assume you are using
> correct naming?
I can confirm that the naming above is fine.
next prev parent reply other threads:[~2024-04-28 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 12:36 [PATCH v2 0/2] arm64: dts: rockchip: Add Radxa ROCK 3C Chukun Pan
2024-04-28 12:36 ` [PATCH v2 1/2] dt-bindings: arm: rockchip: add " Chukun Pan
2024-04-28 16:37 ` Krzysztof Kozlowski
2024-04-28 21:41 ` Dragan Simic [this message]
2024-04-30 10:36 ` Chukun Pan
2024-04-28 12:36 ` [PATCH v2 2/2] arm64: dts: rockchip: Add " Chukun Pan
2024-04-30 5:42 ` Folker Schwesinger
2024-05-02 1:28 ` Dragan Simic
2024-05-02 12:17 ` Jonas Karlman
2024-05-02 13:48 ` Dragan Simic
2024-05-02 17:55 ` Folker Schwesinger
2024-05-03 21:46 ` Jonas Karlman
2024-04-29 14:41 ` [PATCH v2 0/2] " Rob Herring
2024-05-03 11:38 ` Heiko Stuebner
2024-05-03 12:53 ` Heiko Stübner
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=f4baaff6fe20bba48cddb356df6e531a@manjaro.org \
--to=dsimic@manjaro.org \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=krzk@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 \
/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).