Devicetree
 help / color / mirror / Atom feed
From: Dragan Simic <dsimic@manjaro.org>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+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, FUKAUMI Naoki <naoki@radxa.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: correct the model name for Radxa ROCK 3A
Date: Thu, 18 Apr 2024 18:34:45 +0200	[thread overview]
Message-ID: <896b9fa5a87c5724e1f5b8b517227589@manjaro.org> (raw)
In-Reply-To: <d00953aab0f1c978e3720885a6844caa@manjaro.org>

Hello Chukun,

On 2024-04-18 17:21, Dragan Simic wrote:
> On 2024-04-18 15:01, Chukun Pan wrote:
>> According to https://radxa.com/products/rock3/3a,
>> the name of this board should be "Radxa ROCK 3A".
>> Also update compatible to match the model name.
>> 
>> Suggested-by: FUKAUMI Naoki <naoki@radxa.com>
>> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> 
> Looking good to me.  I'll send the remaining naming cleanup patches
> a bit later.

Please note that I didn't touch the ROCK 3 board(s)
in my patches. [1][2]

[1] 
https://lore.kernel.org/linux-rockchip/1e148d6cd4486b31b5e7f3824cf6bccf536b74c0.1713457260.git.dsimic@manjaro.org/
[2] 
https://lore.kernel.org/linux-rockchip/1e148d6cd4486b31b5e7f3824cf6bccf536b74c0.1713457260.git.dsimic@manjaro.org/

>> ---
>>  Documentation/devicetree/bindings/arm/rockchip.yaml | 4 ++--
>>  1 file changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml
>> b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> index 99bd5e2c76a0..88e9e0011953 100644
>> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
>> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
>> @@ -772,9 +772,9 @@ properties:
>>            - const: radxa,rock2-square
>>            - const: rockchip,rk3288
>> 
>> -      - description: Radxa ROCK3 Model A
>> +      - description: Radxa ROCK 3A
>>          items:
>> -          - const: radxa,rock3a
>> +          - const: radxa,rock-3a
>>            - const: rockchip,rk3568
>> 
>>        - description: Radxa ROCK 5 Model A
> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2024-04-18 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-18 13:01 [PATCH 1/2] dt-bindings: arm: rockchip: correct the model name for Radxa ROCK 3A Chukun Pan
2024-04-18 13:01 ` [PATCH 2/2] arm64: dts: " Chukun Pan
2024-04-18 15:21   ` Dragan Simic
2024-04-18 15:21 ` [PATCH 1/2] dt-bindings: arm: " Dragan Simic
2024-04-18 15:37   ` Conor Dooley
2024-04-18 15:46     ` Dragan Simic
2024-04-18 15:57       ` Conor Dooley
2024-04-18 15:58         ` Dragan Simic
2024-04-18 16:34   ` Dragan Simic [this message]
2024-04-18 15:36 ` Conor Dooley

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=896b9fa5a87c5724e1f5b8b517227589@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=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=naoki@radxa.com \
    --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