From: Robert Eshleman <bobbyeshleman@gmail.com>
To: bobbyeshleman@gmail.com
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 2/3] dt-bindings: vendor-prefix: add prefix for Lite-On Corp.
Date: Sun, 24 Feb 2019 12:33:29 -0800 [thread overview]
Message-ID: <f52fc8ffcacc8d80796bc98959b49fe9b0237da8.1551037168.git.bobbyeshleman@gmail.com> (raw)
In-Reply-To: <42dbbd7568e4216a320c6fd617bd91c1ee045af0.1551037168.git.bobbyeshleman@gmail.com>
This patch adds a vendor-prefix for the Lite-On Semiconductor
Corporation.
Signed-off-by: Robert Eshleman <bobbyeshleman@gmail.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 389508584f48..e487a5d95ba9 100644
--- a/Documentation/devicetree/bindings/vendor-prefixes.txt
+++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
@@ -219,6 +219,7 @@ linaro Linaro Limited
linksys Belkin International, Inc. (Linksys)
linux Linux-specific binding
linx Linx Technologies
+liteon Lite-On Semiconductor Corporation
lltc Linear Technology Corporation
logicpd Logic PD, Inc.
lsi LSI Corp. (LSI Logic)
--
2.20.1
next prev parent reply other threads:[~2019-02-24 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-24 20:34 [PATCH v2 1/3] iio: light: Add driver for ap3216c Robert Eshleman
2019-02-24 20:33 ` Robert Eshleman [this message]
2019-02-26 22:40 ` [PATCH v2 2/3] dt-bindings: vendor-prefix: add prefix for Lite-On Corp Rob Herring
2019-02-24 20:33 ` [PATCH v2 3/3] dt-bindings: iio: light: Add ap3216c Robert Eshleman
2019-02-26 22:41 ` Rob Herring
2019-02-27 20:40 ` [PATCH v2 1/3] iio: light: Add driver for ap3216c Tomasz Duszynski
2019-02-28 16:49 ` Sven Van Asbroeck
2019-03-03 14:38 ` Jonathan Cameron
2019-03-04 16:25 ` Sven Van Asbroeck
2019-03-09 17:33 ` Jonathan Cameron
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=f52fc8ffcacc8d80796bc98959b49fe9b0237da8.1551037168.git.bobbyeshleman@gmail.com \
--to=bobbyeshleman@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.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).