From: Marek Vasut <marek.vasut@gmail.com>
To: Matt Ranostay <matt@ranostay.consulting>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Cc: jic23@kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2 1/2] devicetree: add Garmin vendor prefix
Date: Tue, 17 Jan 2017 02:07:56 +0100 [thread overview]
Message-ID: <06f2cde2-ac7e-d0e5-5e35-a4946d0398f8@gmail.com> (raw)
In-Reply-To: <20161229051306.28547-1-matt@ranostay.consulting>
On 12/29/2016 06:13 AM, Matt Ranostay wrote:
Some commit message / description of the company would be useful.
> Cc: Rob Herring <robh@kernel.org>
> Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
> ---
> Changes from v1:
> * switch to stock ticker for Garmin Limited
>
> 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 16d3b5e7f5d1..5749bfc5fc5b 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -107,6 +107,7 @@ firefly Firefly
> focaltech FocalTech Systems Co.,Ltd
> friendlyarm Guangzhou FriendlyARM Computer Tech Co., Ltd
> fsl Freescale Semiconductor
> +grmn Garmin Limited
Why grmn ? Why not 'garmin' ? Also, the rest uses Ltd. , so make it
consistent ?
> ge General Electric Company
> geekbuying GeekBuying
> gef GE Fanuc Intelligent Platforms Embedded Systems, Inc.
>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2017-01-17 1:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 5:13 [PATCH v2 1/2] devicetree: add Garmin vendor prefix Matt Ranostay
2016-12-29 5:13 ` [PATCH v2 2/2] iio: pulsedlight-lidar-lite-v2: add lidar-lite-v3 property Matt Ranostay
2016-12-30 20:26 ` [PATCH v2 1/2] devicetree: add Garmin vendor prefix Jonathan Cameron
2016-12-31 5:55 ` Matt Ranostay
2016-12-31 15:19 ` Jonathan Cameron
2017-01-17 1:07 ` Marek Vasut [this message]
2017-01-17 1:50 ` Matt Ranostay
2017-01-17 1:52 ` Marek Vasut
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=06f2cde2-ac7e-d0e5-5e35-a4946d0398f8@gmail.com \
--to=marek.vasut@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=matt@ranostay.consulting \
--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).