From: Rob Herring <robherring2@gmail.com>
To: David Daney <ddaney.cavm@gmail.com>
Cc: devicetree-discuss@lists.ozlabs.org,
Grant Likely <grant.likely@secretlab.ca>,
linux-kernel@vger.kernel.org,
David Daney <david.daney@cavium.com>
Subject: Re: [PATCH resend] OF/device-tree: Add some entries to vendor-prefixes.txt
Date: Wed, 14 Dec 2011 17:31:12 -0600 [thread overview]
Message-ID: <4EE931C0.30402@gmail.com> (raw)
In-Reply-To: <1323905179-28355-1-git-send-email-ddaney.cavm@gmail.com>
On 12/14/2011 05:26 PM, David Daney wrote:
> From: David Daney <david.daney@cavium.com>
>
> We are currently using 'cavium', 'cortina' and 'st', add them to the
> list of known prefixes.
>
> Signed-off-by: David Daney <david.daney@cavium.com>
Applied.
Rob
> ---
> .../devicetree/bindings/vendor-prefixes.txt | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> index afb9bff..6708797 100644
> --- a/Documentation/devicetree/bindings/vendor-prefixes.txt
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -8,7 +8,9 @@ amcc Applied Micro Circuits Corporation (APM, formally AMCC)
> apm Applied Micro Circuits Corporation (APM)
> arm ARM Ltd.
> atmel Atmel Corporation
> +cavium Cavium, Inc.
> chrp Common Hardware Reference Platform
> +cortina Cortina Systems, Inc.
> dallas Maxim Integrated Products (formerly Dallas Semiconductor)
> denx Denx Software Engineering
> epson Seiko Epson Corp.
> @@ -36,6 +38,7 @@ schindler Schindler
> sil Silicon Image
> simtek
> sirf SiRF Technology, Inc.
> +st STMicroelectronics
> stericsson ST-Ericsson
> ti Texas Instruments
> wlf Wolfson Microelectronics
prev parent reply other threads:[~2011-12-14 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 23:26 David Daney
2011-12-14 23:31 ` Rob Herring [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=4EE931C0.30402@gmail.com \
--to=robherring2@gmail.com \
--cc=david.daney@cavium.com \
--cc=ddaney.cavm@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.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
Powered by JetHome