From: David Lechner <david@lechnology.com>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Cc: David Lechner <david@lechnology.com>,
Sekhar Nori <nsekhar@ti.com>, Kevin Hilman <khilman@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH v4 1/4] dt-bindings: Add vendor prefix for LEGO
Date: Fri, 13 Jan 2017 13:03:39 -0600 [thread overview]
Message-ID: <1484334222-14223-2-git-send-email-david@lechnology.com> (raw)
In-Reply-To: <1484334222-14223-1-git-send-email-david@lechnology.com>
Add a vendor prefix for LEGO Systems A/S
Signed-off-by: David Lechner <david@lechnology.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 61cb272..c1ccfd4 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -159,6 +159,7 @@ kosagi Sutajio Ko-Usagi PTE Ltd.
kyo Kyocera Corporation
lacie LaCie
lantiq Lantiq Semiconductor
+lego LEGO Systems A/S
lenovo Lenovo Group Ltd.
lg LG Corporation
licheepi Lichee Pi
--
2.7.4
next prev parent reply other threads:[~2017-01-13 19:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 19:03 [PATCH v4 0/4] Support for LEGO MINDSTORMS EV3 David Lechner
2017-01-13 19:03 ` David Lechner [this message]
2017-01-18 23:10 ` [PATCH v4 1/4] dt-bindings: Add vendor prefix for LEGO Rob Herring
2017-01-13 19:03 ` [PATCH v4 2/4] dt-bindings: Add LEGO MINDSTORMS EV3 compatible specification David Lechner
2017-01-18 23:11 ` Rob Herring
2017-01-13 19:03 ` [PATCH v4 3/4] dt-bindings: add "microchip,24c128" compatible string David Lechner
2017-01-18 23:11 ` Rob Herring
2017-01-13 19:03 ` [PATCH v4 4/4] ARM: dts: Add LEGO MINDSTORMS EV3 dts David Lechner
2017-01-20 11:48 ` [PATCH v4 0/4] Support for LEGO MINDSTORMS EV3 Sekhar Nori
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=1484334222-14223-2-git-send-email-david@lechnology.com \
--to=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nsekhar@ti.com \
--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).