From: Lars Poeschel <poeschel@lemonage.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: rob.herring@calxeda.com, Pawel Moll <Pawel.Moll@arm.com>,
mark.rutland@arm.com, ian.campbell@citrix.com, rob@landley.net,
Grant Likely <grant.likely@linaro.org>,
arnd@arndb.de, Linus Walleij <linus.walleij@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] of: add vendor prefix for Microchip Technology Inc
Date: Thu, 22 Aug 2013 09:47:29 +0200 [thread overview]
Message-ID: <201308220947.29715.poeschel@lemonage.de> (raw)
In-Reply-To: <5214FBA8.5000603@wwwdotorg.org>
On Wednesday 21 August 2013 at 19:40:56, Stephen Warren wrote:
> On 08/21/2013 09:19 AM, Lars Poeschel wrote:
> > Trivial patch to add Microchip Technology Inc. to the list
> > of devicetree vendor prefixes, as it is already used in
> > Documentation/devicetree/bindings/gpio/gpio-mcp23s08.txt
>
> Oh dear. Perhaps it can be legacy-ified...
>
> > diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
> >
> > +mcp Microchip Technology Inc.
>
> If I saw "mcp," in a *.dts file, I wouldn't immediately think
> "Microchip".
>
> Their stock ticker appears to be MCHP, so I'd suggest either "mchp" or
> "microchip" instead; that latter being my personal preference.
Any other opinions?
If there are other voices who don't like it, we can change it. There is no
in-tree dts file using this yet.
How can a renaming be done? Would that involve changing the drivers (and
module) name too? Or do we have the difference between "mcp" in the drivers
name and "microchip" for device tree properties? In the latter case, I'd
vote against it - if anyone cares. ;-)
Lars
next prev parent reply other threads:[~2013-08-22 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 15:19 Lars Poeschel
2013-08-21 17:40 ` Stephen Warren
2013-08-22 7:47 ` Lars Poeschel [this message]
2013-08-22 7:52 ` Florian Fainelli
2013-08-22 9:03 ` Lars Poeschel
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=201308220947.29715.poeschel@lemonage.de \
--to=poeschel@lemonage.de \
--cc=Pawel.Moll@arm.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=swarren@wwwdotorg.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
all inboxes | Powered by JetHome®