From: David Wang <David_Wang6097@jabil.com>
To: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <edward_chen@jabil.com>, <ben_pai@jabil.com>,
David Wang <David_Wang6097@jabil.com>
Subject: [PATCH 3/3] dt-bindings: vendor-prefixes: document jabil vendors for Aspeed BMC boards
Date: Wed, 1 Jun 2022 16:08:56 +0800 [thread overview]
Message-ID: <20220601080856.1548851-3-David_Wang6097@jabil.com> (raw)
In-Reply-To: <20220601080856.1548851-1-David_Wang6097@jabil.com>
Depends on Krzysztof Kozlowski's vendor prefix patch
Added Jabil vendor prefix for Aspeed SoC based BMC board manufacturers.
---
v2
- Change the order of items
---
Signed-off-by: David Wang <David_Wang6097@jabil.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 169f11ce4cc5..1bd23060dcf9 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -626,6 +626,8 @@ patternProperties:
description: ITian Corporation
"^iwave,.*":
description: iWave Systems Technologies Pvt. Ltd.
+ "^jabil,.*":
+ description: Jabil Design Service Branch (Sanchong)
"^jdi,.*":
description: Japan Display Inc.
"^jedec,.*":
--
2.30.2
next prev parent reply other threads:[~2022-06-01 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 8:08 [PATCH 1/3] ARM: dts: aspeed: Adding Jabil Rubypass BMC David Wang
2022-06-01 8:08 ` [PATCH v5 3/3] dt-bindings: arm: aspeed: document board compatibles David Wang
2022-06-01 8:21 ` Krzysztof Kozlowski
2022-06-01 8:08 ` David Wang [this message]
2022-06-01 8:28 ` [PATCH 3/3] dt-bindings: vendor-prefixes: document jabil vendors for Aspeed BMC boards Krzysztof Kozlowski
2022-06-01 8:29 ` [PATCH 1/3] ARM: dts: aspeed: Adding Jabil Rubypass BMC 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=20220601080856.1548851-3-David_Wang6097@jabil.com \
--to=david_wang6097@jabil.com \
--cc=ben_pai@jabil.com \
--cc=devicetree@vger.kernel.org \
--cc=edward_chen@jabil.com \
--cc=krzysztof.kozlowski+dt@linaro.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 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.