From: Shawn Guo <shawnguo@kernel.org>
To: Joshua Clayton <stillcompiling@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
Sascha Hauer <kernel@pengutronix.de>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] of: add vendor prefix for UniWest
Date: Mon, 1 Feb 2016 19:21:53 +0800 [thread overview]
Message-ID: <20160201112153.GD10671@tiger> (raw)
In-Reply-To: <b11bf2208fe30b96c4d82e634e8abe04343754de.1452717014.git.stillcompiling@gmail.com>
On Wed, Jan 13, 2016 at 12:45:11PM -0800, Joshua Clayton wrote:
> United Western Technologies Corp, known primarily as UniWest,
> is a manufacturer of eddy current and ultrasonic testing equipment.
>
> Signed-off-by: Joshua Clayton <stillcompiling@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 55df1d4..7dabdee 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -230,6 +230,7 @@ toradex Toradex AG
> toshiba Toshiba Corporation
> toumaz Toumaz
> tplink TP-LINK Technologies Co., Ltd.
> +uniwest United Western Technologies Corp (UniWest)
As far as I know, it should be added in alphabetical order.
Shawn
> tronfy Tronfy
> truly Truly Semiconductors Limited
> upisemi uPI Semiconductor Corp.
> --
> 2.5.0
>
>
next prev parent reply other threads:[~2016-02-01 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 20:45 [PATCH 1/2] of: add vendor prefix for UniWest Joshua Clayton
2016-01-13 20:45 ` [PATCH 2/2] ARM: dts: Add dts for Uniwest evi Joshua Clayton
[not found] ` <66c87b9536b674bdedfdbe2306def8e9bf6a585c.1452717014.git.stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-01 12:11 ` Shawn Guo
2016-02-02 21:21 ` Joshua Clayton
2016-02-02 22:13 ` [PATCH v2] " Joshua Clayton
[not found] ` <1454451202-1687-1-git-send-email-stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-03 9:24 ` Philipp Zabel
[not found] ` <1454491459.3415.6.camel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2016-02-03 17:37 ` [PATCH v3] " Joshua Clayton
[not found] ` <1454521065-14241-1-git-send-email-stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-02-14 3:28 ` Shawn Guo
[not found] ` <b11bf2208fe30b96c4d82e634e8abe04343754de.1452717014.git.stillcompiling-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-01-13 23:37 ` [PATCH 1/2] of: add vendor prefix for UniWest Rob Herring
[not found] ` <CAL_JsqKLDZ55XtA2fsy_0s50wA-o_cvwgFNb5Y+Qq14ErJJbJA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-13 23:51 ` Joshua Clayton
2016-02-01 11:21 ` Shawn Guo [this message]
2016-02-01 11:54 ` Joshua Clayton
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=20160201112153.GD10671@tiger \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=stillcompiling@gmail.com \
/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).