From: Dianlong Li <long17.cool@163.com>
To: robh@kernel.org
Cc: alexandre.belloni@bootlin.com, a.zummo@towertech.it,
mark.rutland@arm.com, linux-rtc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Dianlong Li <long17.cool@163.com>
Subject: [PATCH 1/3] dt-bindings: define vendor prefix for whwave, Inc.
Date: Thu, 13 Dec 2018 18:13:48 +0800 [thread overview]
Message-ID: <1544696030-17159-1-git-send-email-long17.cool@163.com> (raw)
Introduce vendor prefix for whwave, Inc.
for SD3078 rtc device.
Signed-off-by: Dianlong Li <long17.cool@163.com>
---
.../devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 4b1a2a8..89403c7 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -423,6 +423,7 @@ vot Vision Optical Technology Co., Ltd.
wd Western Digital Corp.
wetek WeTek Electronics, limited.
wexler Wexler
+whwave Shenzhen whwave Electronics, Inc.
wi2wi Wi2Wi, Inc.
winbond Winbond Electronics corp.
winstar Winstar Display Corp.
--
1.7.9.5
next reply other threads:[~2018-12-13 10:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 10:13 Dianlong Li [this message]
2018-12-13 10:13 ` [PATCH 2/3] dt-bindings: rtc: sd3078: add device tree documentation Dianlong Li
2018-12-20 20:26 ` Rob Herring
2018-12-13 10:13 ` [PATCH 3/3] rtc: sd3078: new driver Dianlong Li
2019-01-10 20:57 ` Alexandre Belloni
2018-12-20 20:25 ` [PATCH 1/3] dt-bindings: define vendor prefix for whwave, Inc Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2018-11-23 10:14 zoro
2018-12-11 21:37 ` Rob Herring
2018-12-11 21:41 ` Rob Herring
2018-11-14 9:17 zoro
2018-11-12 18:03 zoro
2018-11-10 8:43 zoro
2018-11-10 12:19 ` Alexandre Belloni
2018-11-10 8:40 zoro
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=1544696030-17159-1-git-send-email-long17.cool@163.com \
--to=long17.cool@163.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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).