From: Matus Gajdos <matuszpd@gmail.com>
To: Pavel Machek <pavel@ucw.cz>, Lee Jones <lee@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Matus Gajdos <matuszpd@gmail.com>
Subject: [PATCH 1/3] dt-bindings: Add vendor prefix for Broadchip Technology Group Co., Ltd.
Date: Thu, 27 Jul 2023 18:05:23 +0200 [thread overview]
Message-ID: <20230727160525.23312-2-matuszpd@gmail.com> (raw)
In-Reply-To: <20230727160525.23312-1-matuszpd@gmail.com>
Website: http://www.broadchip.com
Signed-off-by: Matus Gajdos <matuszpd@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 af60bf1a6664..dc1ed3dc0c9f 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -202,6 +202,8 @@ patternProperties:
description: Bosch Sensortec GmbH
"^boundary,.*":
description: Boundary Devices Inc.
+ "^broadchip,.*":
+ description: Broadchip Technology Group Co., Ltd.
"^brcm,.*":
description: Broadcom Corporation
"^broadmobi,.*":
--
2.25.1
next prev parent reply other threads:[~2023-07-27 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 16:05 [PATCH 0/3] leds: Add Broadchip BCT3024 LED driver Matus Gajdos
2023-07-27 16:05 ` Matus Gajdos [this message]
2023-07-28 7:29 ` [PATCH 1/3] dt-bindings: Add vendor prefix for Broadchip Technology Group Co., Ltd Krzysztof Kozlowski
2023-07-27 16:05 ` [PATCH 2/3] dt-bindings: leds: Add binding for Broadchip BCT3024 LED driver Matus Gajdos
2023-07-28 7:31 ` Krzysztof Kozlowski
2023-07-27 16:05 ` [PATCH 3/3] leds: Add " Matus Gajdos
2023-07-28 4:20 ` kernel test robot
2023-07-28 7:41 ` 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=20230727160525.23312-2-matuszpd@gmail.com \
--to=matuszpd@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).