From: dillon.minfei@gmail.com
To: festevam@gmail.com, shawnguo@kernel.org, s.riedmueller@phytec.de,
matthias.schiffer@ew.tq-group.com, leoyang.li@nxp.com,
arnd@arndb.de, olof@lixom.net, s.hauer@pengutronix.de,
kernel@pengutronix.de, prabhakar.csengg@gmail.com,
mchehab@kernel.org, mchehab+huawei@kernel.org
Cc: krzysztof.kozlowski@canonical.com, krzk@kernel.org,
robh+dt@kernel.org, linux@rempel-privat.de,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-imx@nxp.com,
linux-media@vger.kernel.org, Dillon Min <dillon.minfei@gmail.com>
Subject: [PATCH v5 1/4] dt-bindings: add dasheng vendor prefix
Date: Tue, 4 May 2021 13:09:50 +0800 [thread overview]
Message-ID: <1620104993-5850-2-git-send-email-dillon.minfei@gmail.com> (raw)
In-Reply-To: <1620104993-5850-1-git-send-email-dillon.minfei@gmail.com>
From: Dillon Min <dillon.minfei@gmail.com>
Add vendor prefix for DaSheng, Inc.
Signed-off-by: Dillon Min <dillon.minfei@gmail.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Acked-by: Rob Herring <robh@kernel.org>
---
v5:
- no code change, just change my git author name from lower case to higher case
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 f6064d84a424..4ec28488c963 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.yaml
+++ b/Documentation/devicetree/bindings/vendor-prefixes.yaml
@@ -309,6 +309,8 @@ patternProperties:
description: DPTechnics
"^dragino,.*":
description: Dragino Technology Co., Limited
+ "^ds,.*":
+ description: DaSheng, Inc.
"^dserve,.*":
description: dServe Technology B.V.
"^dynaimage,.*":
--
1.9.1
next prev parent reply other threads:[~2021-05-04 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 5:09 [PATCH v5 0/4] arm: imx: Add i.mx6q DaSheng COM-9XX SBC board support dillon.minfei
2021-05-04 5:09 ` dillon.minfei [this message]
2021-05-23 2:20 ` [PATCH v5 1/4] dt-bindings: add dasheng vendor prefix Shawn Guo
2021-05-04 5:09 ` [PATCH v5 2/4] dt-bindings: arm: imx: Add i.mx6q DaSheng COM-9XX SBC dillon.minfei
2021-05-23 2:21 ` Shawn Guo
2021-05-04 5:09 ` [PATCH v5 3/4] arm: dts: imx: Add i.mx6q DaSheng COM-9XX SBC board support dillon.minfei
2021-05-11 15:18 ` Dillon Min
2021-05-23 2:25 ` Shawn Guo
2021-05-23 2:34 ` Dillon Min
2021-05-04 5:09 ` [PATCH v5 4/4] media: i2c: ov2659: Use clk_{prepare_enable,disable_unprepare}() to set xvclk on/off dillon.minfei
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=1620104993-5850-2-git-send-email-dillon.minfei@gmail.com \
--to=dillon.minfei@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=matthias.schiffer@ew.tq-group.com \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=olof@lixom.net \
--cc=prabhakar.csengg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s.riedmueller@phytec.de \
--cc=shawnguo@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).