linux-kernel - Re: [PATCH] arm64: dts: rockchip: Add dtsi file for RK3399S SoC variant

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <ff3e9357b9014a217ace90703688758a@manjaro.org>
Date: Fri, 11 Oct 2024 08:56:07 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Heiko Stübner <heiko@...ech.de>
Cc: linux-rockchip@...ts.infradead.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 devicetree@...r.kernel.org, robh@...nel.org, krzk+dt@...nel.org,
 conor+dt@...nel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add dtsi file for RK3399S SoC
 variant

Hello Heiko,

On 2024-10-10 22:24, Heiko Stübner wrote:
> Am Mittwoch, 9. Oktober 2024, 16:06:00 CEST schrieb Dragan Simic:
>> The way the introduced RK3399S SoC variant dtsi file (rk3399s.dtsi) is 
>> named
>> diverges from the way the two already present RK3399 SoC variant dtsi 
>> files
>> (rk3399-op1.dtsi and rk3399-t.dtsi) are named, but that simply follows 
>> the
>> commonly used and/or the official RK3399 SoC variant names.
> 
> This is my only gripe with this ;-) .
> 
> I.e. looking through simple google, the rk3399t also seems to be 
> written
> without "-" most of the time.
> 
> Though for me it would make the most sense to just go with "rk3399-s"
> here for some sort of clear style between -s -t and -op1

Believe it or not, the inconsistency of having no dash before the "s"
has bothered me too. :)  Let's add the dash, which I'll do in the v2.