From: Nicolas Ferre <nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] devicetree: Add a registry of vendor prefixes
Date: Thu, 22 Sep 2011 10:00:23 +0200 [thread overview]
Message-ID: <4E7AEB17.9010009@atmel.com> (raw)
In-Reply-To: <20110921152324.15993.96272.stgit@ponder>
Hi Grant,
Le 21/09/2011 17:23, Grant Likely :
> There is no centralized listing for the in-use vendor prefixes
> used in compatible strings and property names. This patch adds one.
> New prefixes should get added to this list to reduce the likelyhood
> of namespace collisions.
>
> Signed-off-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
> ---
> .../devicetree/bindings/vendor-prefixes.txt | 38 ++++++++++++++++++++
> 1 files changed, 38 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/vendor-prefixes.txt
>
> diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt b/Documentation/devicetree/bindings/vendor-prefixes.txt
> new file mode 100644
> index 0000000..81465c1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/vendor-prefixes.txt
> @@ -0,0 +1,38 @@
> +Device tree binding vendor prefix registry. Keep list in alphabetical order.
> +
> +This isn't an exhaustive list, but you should add new prefixes to it before
> +using them to avoid name-space collisions.
> +
> +adi Analog Devices, Inc.
> +amcc Applied Micro Circuits Corporation (APM, formally AMCC)
> +apm Applied Micro Circuits Corporation (APM)
> +arm ARM Ltd.
Can we add:
+atmel Atmel Corporation
I am working on a revival of patches that I have cooked at Linaro
Connect for AT91...
Best regards,
--
Nicolas Ferre
prev parent reply other threads:[~2011-09-22 8:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 15:23 [PATCH] devicetree: Add a registry of vendor prefixes Grant Likely
2011-09-21 20:38 ` David Brown
[not found] ` <20110921203853.GA2824-AOX6H5vLt3Uj8izMo0bVsAC/G2K4zDHf@public.gmane.org>
2011-09-21 20:53 ` Grant Likely
[not found] ` <20110921205336.GD17168-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>
2011-09-21 22:51 ` David Brown
[not found] ` <20110921225100.GA20726-AOX6H5vLt3Uj8izMo0bVsAC/G2K4zDHf@public.gmane.org>
2011-09-22 1:56 ` Grant Likely
2011-09-22 8:00 ` Nicolas Ferre [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=4E7AEB17.9010009@atmel.com \
--to=nicolas.ferre-aife0yeh4naavxtiumwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.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).