All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, Dragan Simic <dsimic@manjaro.org>
Cc: 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: Thu, 10 Oct 2024 22:24:33 +0200	[thread overview]
Message-ID: <46729153.fMDQidcC6G@diego> (raw)
In-Reply-To: <59c524a9a12465c21e01b779b42749fae148c41d.1728482151.git.dsimic@manjaro.org>

Hi Dragan,

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


Heiko




_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org, Dragan Simic <dsimic@manjaro.org>
Cc: 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: Thu, 10 Oct 2024 22:24:33 +0200	[thread overview]
Message-ID: <46729153.fMDQidcC6G@diego> (raw)
In-Reply-To: <59c524a9a12465c21e01b779b42749fae148c41d.1728482151.git.dsimic@manjaro.org>

Hi Dragan,

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


Heiko





  reply	other threads:[~2024-10-10 20:41 UTC|newest]

Thread overview: 6+ 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-09 14:06 ` Dragan Simic
2024-10-10 20:24 ` Heiko Stübner [this message]
2024-10-10 20:24   ` Heiko Stübner
2024-10-11  6:56   ` Dragan Simic
2024-10-11  6:56     ` Dragan Simic

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=46729153.fMDQidcC6G@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.