From: Sam Edwards <cfsworks@gmail.com>
To: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh+dt@kernel.org>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Daniel Kukieła" <daniel@kukiela.pl>,
"Sven Rademakers" <sven.rademakers@gmail.com>,
"Lokesh Poovaragan" <loki@gimmeapis.com>,
"Sam Edwards" <CFSworks@gmail.com>
Subject: [PATCH 1/3] dt-bindings: vendor-prefixes: add turing
Date: Fri, 6 Oct 2023 22:35:58 -0600 [thread overview]
Message-ID: <20231007043600.151908-2-CFSworks@gmail.com> (raw)
In-Reply-To: <20231007043600.151908-1-CFSworks@gmail.com>
Add vendor prefix for Turing Machines, Inc.
(https://turingpi.com)
Signed-off-by: Sam Edwards <CFSworks@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 573578db9509..07f164e1ca2e 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -1420,6 +1420,8 @@ patternProperties:
description: Truly Semiconductors Limited
"^tsd,.*":
description: Theobroma Systems Design und Consulting GmbH
+ "^turing,.*":
+ description: Turing Machines, Inc.
"^tyan,.*":
description: Tyan Computer Corporation
"^u-blox,.*":
--
2.41.0
next prev parent reply other threads:[~2023-10-07 4:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 4:35 [PATCH 0/3] Add initial devicetree for Turing RK1 Sam Edwards
2023-10-07 4:35 ` Sam Edwards [this message]
2023-10-10 14:19 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add turing Rob Herring
2023-10-07 4:35 ` [PATCH 2/3] dt-bindings: arm: rockchip: Add Turing RK1 Sam Edwards
2023-10-07 4:36 ` [PATCH 3/3] arm64: dts: rockchip: Add Turing RK1 SoM support Sam Edwards
2023-10-08 12:59 ` Heiko Stübner
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=20231007043600.151908-2-CFSworks@gmail.com \
--to=cfsworks@gmail.com \
--cc=daniel@kukiela.pl \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=loki@gimmeapis.com \
--cc=robh+dt@kernel.org \
--cc=sven.rademakers@gmail.com \
/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).