From: Guo Ren <ren_guo@c-sky.com>
To: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, daniel.lezcano@linaro.org,
jason@lakedaemon.net, arnd@arndb.de, devicetree@vger.kernel.org,
andrea.parri@amarulasolutions.com, peterz@infradead.org
Cc: c-sky_gcc_upstream@c-sky.com, gnu-csky@mentor.com,
thomas.petazzoni@bootlin.com, wbx@uclibc-ng.org,
ren_guo@c-sky.com, green.hu@gmail.com
Subject: [PATCH V4 27/27] dt-bindings: Add vendor prefix for csky
Date: Wed, 12 Sep 2018 22:52:09 +0800 [thread overview]
Message-ID: <21c4e62bed6dcb4ff8ee860fb53de69a0adb1cce.1536758961.git.ren_guo@c-sky.com> (raw)
In-Reply-To: <93e8b592e429c156ad4d4ca5d85ef48fd0ab8b70.1536758961.git.ren_guo@c-sky.com>
In-Reply-To: <cover.1536758961.git.ren_guo@c-sky.com>
Signed-off-by: Guo Ren <ren_guo@c-sky.com>
---
Documentation/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 7cad066..335f9e0 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -81,6 +81,7 @@ cosmic Cosmic Circuits
crane Crane Connectivity Solutions
creative Creative Technology Ltd
crystalfontz Crystalfontz America, Inc.
+csky Hangzhou C-SKY Microsystems Co., Ltd
cubietech Cubietech, Ltd.
cypress Cypress Semiconductor Corporation
cznic CZ.NIC, z.s.p.o.
--
2.7.4
prev parent reply other threads:[~2018-09-12 14:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1536758961.git.ren_guo@c-sky.com>
2018-09-12 14:51 ` [PATCH V4 11/27] csky: Atomic operations Guo Ren
2018-09-12 14:51 ` [PATCH V4 12/27] csky: ELF and module probe Guo Ren
2018-09-12 14:51 ` [PATCH V4 13/27] csky: Library functions Guo Ren
2018-09-12 14:51 ` [PATCH V4 14/27] csky: User access Guo Ren
2018-09-12 14:51 ` [PATCH V4 15/27] csky: Debug and Ptrace GDB Guo Ren
2018-09-12 14:51 ` [PATCH V4 16/27] csky: SMP support Guo Ren
2018-09-12 14:51 ` [PATCH V4 17/27] csky: Misc headers Guo Ren
2018-09-12 14:52 ` [PATCH V4 18/27] dt-bindings: csky CPU Bindings Guo Ren
2018-09-12 14:52 ` [PATCH V4 19/27] dt-bindings: timer: gx6605s SOC timer Guo Ren
2018-09-12 14:52 ` [PATCH V4 20/27] dt-bindings: timer: C-SKY Multi-processor timer Guo Ren
2018-09-12 14:52 ` [PATCH V4 21/27] dt-bindings: interrupt-controller: C-SKY APB intc Guo Ren
2018-09-12 14:52 ` [PATCH V4 22/27] dt-bindings: interrupt-controller: C-SKY SMP intc Guo Ren
2018-09-12 14:52 ` [PATCH V4 23/27] clocksource: add gx6605s SOC system timer Guo Ren
2018-09-12 14:52 ` [PATCH V4 24/27] clocksource: add C-SKY SMP timer Guo Ren
2018-09-12 14:52 ` [PATCH V4 25/27] clocksource: add C-SKY timers' build infrastructure Guo Ren
2018-09-12 14:52 ` [PATCH V4 26/27] irqchip: add C-SKY irqchip drivers Guo Ren
2018-09-12 14:52 ` Guo Ren [this message]
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=21c4e62bed6dcb4ff8ee860fb53de69a0adb1cce.1536758961.git.ren_guo@c-sky.com \
--to=ren_guo@c-sky.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=arnd@arndb.de \
--cc=c-sky_gcc_upstream@c-sky.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=gnu-csky@mentor.com \
--cc=green.hu@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@bootlin.com \
--cc=wbx@uclibc-ng.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).