devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Brian Dodge <bdodge09@gmail.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: arc vendor prefix
Date: Tue, 25 Sep 2018 10:23:08 -0500	[thread overview]
Message-ID: <20180925152308.GA21227@bogus> (raw)
In-Reply-To: <20180920130952.7eb8e45c@alans-desktop>

On Thu, Sep 20, 2018 at 01:09:52PM +0100, Alan Cox wrote:
> On Tue, 18 Sep 2018 21:05:20 -0400
> Brian Dodge <bdodge09@gmail.com> wrote:
> 
> > Hi,
> > 
> > In the linux kernel commit 91ab076e3a2f092254fe5231bbfa92b37fd52e38 the 
> > vendor prefix "arctic" was added to vendor-prefixes.txt.
> > 
> > The original change I authored used "arc" not "arctic", and the device 
> > tree bindings were added assuming that prefix in commit 
> > ce9d22573d85341c987f997461ac712e4dbe47b1
> > 
> > Perhaps odeju changed the name to arctic in the patch after I created it 
> > and before it was approved.
> > 
> > This pairing isn't really compatible is it?  Either the prefix should be 
> > reverted to "arc" or the bindings (and driver source) changed to use 
> > "arctic", as in "arctic,arc2c0608" vs. "arc,arc2c0608"
> 
> ARC is a Synopsys registered trademark for the ARC processor line. I'm not
> sure what the right answer is but I think it might be better to keep to
> arctic to avoid confusion with arc based products.

Agreed.

Rob

      reply	other threads:[~2018-09-25 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19  1:05 arc vendor prefix Brian Dodge
2018-09-20 12:09 ` Alan Cox
2018-09-25 15:23   ` 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=20180925152308.GA21227@bogus \
    --to=robh@kernel.org \
    --cc=bdodge09@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).