From: Jordan Chang <jordan.chang@ufispace.com>
To: linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org, joel@jms.id.au,
andrew@aj.id.au, robh+dt@kernel.org
Cc: jay.tc.lin@ufispace.com, eason.ys.huang@ufispace.com
Subject: [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add prefix for Ufi Space
Date: Thu, 2 Feb 2023 16:18:41 +0800 [thread overview]
Message-ID: <20230202081843.2358-2-jordan.chang@ufispace.com> (raw)
In-Reply-To: <20230202081843.2358-1-jordan.chang@ufispace.com>
Add a vendor prefix for Ufi Space (https://www.ufispace.com).
Signed-off-by: Jordan Chang <jordan.chang@ufispace.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 2f0151e9f6be..ab0dd1cb5ede 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -1344,6 +1344,8 @@ patternProperties:
description: Ubiquiti Networks
"^udoo,.*":
description: Udoo
+ "^ufispace,.*":
+ description: Ufi Space Co., Ltd.
"^ugoos,.*":
description: Ugoos Industrial Co., Ltd.
"^uniwest,.*":
--
2.39.0
next prev parent reply other threads:[~2023-02-02 8:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 8:18 [PATCH v2 0/3] Add Ufispace NCPLite platform device tree Jordan Chang
2023-02-02 8:18 ` Jordan Chang [this message]
2023-02-08 10:28 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add prefix for Ufi Space Krzysztof Kozlowski
2023-02-02 8:18 ` [PATCH v2 2/3] dt-bindings: arm: aspeed: document Ufispace NCPLite BMC Jordan Chang
2023-02-08 10:28 ` Krzysztof Kozlowski
2023-02-02 8:18 ` [PATCH v2 3/3] ARM: dts: aspeed: Add device tree for " Jordan Chang
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=20230202081843.2358-2-jordan.chang@ufispace.com \
--to=jordan.chang@ufispace.com \
--cc=andrew@aj.id.au \
--cc=eason.ys.huang@ufispace.com \
--cc=jay.tc.lin@ufispace.com \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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®