devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: David Brown <davidb-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] devicetree: Add a registry of vendor prefixes
Date: Wed, 21 Sep 2011 15:51:00 -0700	[thread overview]
Message-ID: <20110921225100.GA20726@huya.qualcomm.com> (raw)
In-Reply-To: <20110921205336.GD17168-e0URQFbLeQY2iJbIjFUEsiwD8/FfD2ys@public.gmane.org>

On Wed, Sep 21, 2011 at 02:53:36PM -0600, Grant Likely wrote:
> On Wed, Sep 21, 2011 at 01:38:54PM -0700, David Brown wrote:
> > On Wed, Sep 21, 2011 at 09:23:25AM -0600, Grant Likely wrote:
> > > 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.
> > > 
> > > +powervr	Imagination Technologies
> > > +ramtron	Ramtron International
> > 
> > qcom is already used by the patches I sent out (and should be in the
> > soc tree).  I can make a patch for that, but I guess I first need to
> > ask around here for what company name we should use.
> 
> This isn't any kind of "authoritative" list, and it represents who
> makes the components, not who writes the code.  I'll use Qualcomm.

Probably Qualcomm, Inc or Qualcomm Incorporated would be best, but if
you make the change (rather than me) it matters less.

David

  parent reply	other threads:[~2011-09-21 22:51 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 [this message]
     [not found]           ` <20110921225100.GA20726-AOX6H5vLt3Uj8izMo0bVsAC/G2K4zDHf@public.gmane.org>
2011-09-22  1:56             ` Grant Likely
2011-09-22  8:00 ` Nicolas Ferre

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=20110921225100.GA20726@huya.qualcomm.com \
    --to=davidb-sgv2jx0feol9jmxxk+q4oq@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).