From: Coia Prant <coiaprant@gmail.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Dragan Simic <dsimic@manjaro.org>,
Jonas Karlman <jonas@kwiboo.se>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add NineTripod
Date: Thu, 30 Oct 2025 02:00:23 +0800 [thread overview]
Message-ID: <8C82BBEB-2302-49F7-A441-600014D7E250@gmail.com> (raw)
In-Reply-To: <20251029-reseller-unsavory-5461fe7f6cce@spud>
On October 30, 2025 1:24:55 AM GMT+08:00, Conor Dooley <conor@kernel.org> wrote:
>On Tue, Oct 28, 2025 at 01:04:32PM -0700, Coia Prant wrote:
>> There won't be any problems at the moment.
>
>Please stop top posting.
>
>> Just out of habit (because when writing code, variable names cannot
>> begin with a number)
>> There may be some misimplemented parsers that cannot do this.
>>
>> As a practical matter, the branch of openwrt has added support for
>> this board in advance, and openwrt uses the DTS name to initialize
>> some default settings such as LEDs and bridge
>
>That sounds like a problem with the WRT development process. This is a
>trivial change, there could be more disruptive things required to
>satisfy reviewers. Why was it submitted there in advance anyway?
>
>> I'm not sure if he will affect the version that has been released.
>> But maybe it's not a big problem.
>>
>> If you feel that there is no problem, I can send a new set of patches
>> to fix this problem.
>
>Please do.
>
>> 2025-10-28 19:46 (GMT+00:00), Conor Dooley <conor@kernel.org> said:
>> > On Tue, Oct 28, 2025 at 12:38:10PM -0700, Coia Prant wrote:
>> > At first, it was to avoid problems with the beginning of numbers.
>> > What problems does starting with a number produce?
>> > Given that it is already used by downstream projects, we have retained
>> > this to ensure that users can seamlessly migrate to the mainline
>> > version.
>> > What's the actual impact of changing it from "nine" to "9" for
>> > downstream users? This is a board vendor, probably nothing is even
>> > interacting with the board-level compatible at all programmatically?
>> > Please don't top post.
>> > Thanks.
>> >
>> > 2025-10-28 19:35 (GMT+00:00), Conor Dooley said:
>> > On Sun, Oct 26, 2025 at 10:36:44PM +0800, Coia Prant wrote:
>> > Add NineTripod to the vendor prefixes.
>> >
>> > Signed-off-by: Coia Prant
>> > ---
>> > Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
>> > 1 file changed, 2 insertions(+)
>> >
>> > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> > b/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> > index f1d188200..37687737e 100644
>> > --- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> > +++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
>> > @@ -1124,6 +1124,8 @@ patternProperties:
>> > description: National Instruments
>> > "^nicera,.*":
>> > description: Nippon Ceramic Co., Ltd.
>> > + "^ninetripod,.*":
>> > Why ninetripod instead of 9tripod? That's what the company uses and in
>> > the marketing fluff for the boards.
>> > + description: Shenzhen 9Tripod Innovation and Development CO., LTD.
>> > "^nintendo,.*":
>> > description: Nintendo
>> > "^nlt,.*":
>> > --
>> > 2.47.3
>> >
Sorry.
I already switch to a new mali client which support bottom posting.
I will send new patches after test with install PCIe CLK.
Wish have a good day.
:)
next prev parent reply other threads:[~2025-10-29 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 14:36 Coia Prant
2025-10-26 14:36 ` [PATCH v3 2/3] dt-bindings: arm: rockchip: Add NineTripod X3568 series Coia Prant
2025-10-26 14:36 ` [PATCH v3 3/3] arm64: dts: rockchip: Add devicetree for the NineTripod X3568 v4 Coia Prant
2025-10-28 19:35 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add NineTripod Conor Dooley
2025-10-28 19:38 ` Coia Prant
2025-10-28 19:46 ` Conor Dooley
2025-10-28 20:04 ` Coia Prant
2025-10-29 17:24 ` Conor Dooley
2025-10-29 18:00 ` Coia Prant [this message]
2025-10-28 19:42 ` Coia Prant
2025-10-28 21:07 ` Krzysztof Kozlowski
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=8C82BBEB-2302-49F7-A441-600014D7E250@gmail.com \
--to=coiaprant@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=jonas@kwiboo.se \
--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
all inboxes | Powered by JetHome®