From: Dragan Simic <dsimic@manjaro.org>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: Add dtsi file for RK3399S SoC variant
Date: Fri, 11 Oct 2024 08:56:07 +0200 [thread overview]
Message-ID: <ff3e9357b9014a217ace90703688758a@manjaro.org> (raw)
In-Reply-To: <46729153.fMDQidcC6G@diego>
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.
prev parent reply other threads:[~2024-10-11 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 14:06 [PATCH] arm64: dts: rockchip: Add dtsi file for RK3399S SoC variant Dragan Simic
2024-10-10 20:24 ` Heiko Stübner
2024-10-11 6:56 ` Dragan Simic [this message]
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=ff3e9357b9014a217ace90703688758a@manjaro.org \
--to=dsimic@manjaro.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 \
/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