From: Jun Yan <jerrysteve1101@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
heiko@sntech.de, quentin.schulz@cherry.de, dsimic@manjaro.org,
naoki@radxa.com
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Jun Yan <jerrysteve1101@gmail.com>
Subject: [PATCH 1/3] dt-bindings: vendor-prefixes: Add Shenzhen OneThing Technologies Co., Ltd.
Date: Mon, 14 Jul 2025 00:32:53 +0800 [thread overview]
Message-ID: <20250713163255.163669-2-jerrysteve1101@gmail.com> (raw)
In-Reply-To: <20250713163255.163669-1-jerrysteve1101@gmail.com>
OneThing is a company engaged in edge computing.
Signed-off-by: Jun Yan <jerrysteve1101@gmail.com>
---
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 5d2a7a8d3ac6..77fbbe040706 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -1108,6 +1108,8 @@ patternProperties:
description: OLIMEX Ltd.
"^olpc,.*":
description: One Laptop Per Child
+ "^onething,.*":
+ descriotion: Shenzhen OneThing Technologies Co., Ltd.
"^oneplus,.*":
description: OnePlus Technology (Shenzhen) Co., Ltd.
"^onie,.*":
--
2.50.1
next prev parent reply other threads:[~2025-07-13 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 16:32 [PATCH 0/3] board: rockchip: add OneThing Cloud OEC turbo Jun Yan
2025-07-13 16:32 ` Jun Yan [this message]
2025-07-13 17:28 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add Shenzhen OneThing Technologies Co., Ltd Rob Herring (Arm)
2025-07-13 18:57 ` Heiko Stübner
2025-07-13 16:32 ` [PATCH 2/3] dt-bindings: arm: rockchip: Add OneThing Cloud OEC turbo Jun Yan
2025-07-15 3:33 ` Rob Herring (Arm)
2025-07-13 16:32 ` [PATCH 3/3] arm64: dts: " Jun Yan
2025-07-13 16:48 ` Andrew Lunn
2025-07-14 6:02 ` 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=20250713163255.163669-2-jerrysteve1101@gmail.com \
--to=jerrysteve1101@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dsimic@manjaro.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=naoki@radxa.com \
--cc=quentin.schulz@cherry.de \
--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;
as well as URLs for NNTP newsgroup(s).