linux-kernel - Re: [PATCH] of: add vendor prefix for Microchip Technology Inc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 22 Aug 2013 11:03:49 +0200
From:	Lars Poeschel <poeschel@...onage.de>
To:	Florian Fainelli <f.fainelli@...il.com>
Cc:	Stephen Warren <swarren@...dotorg.org>,
	Rob Herring <rob.herring@...xeda.com>,
	Pawel Moll <Pawel.Moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ian.campbell@...rix.com>,
	Rob Landley <rob@...dley.net>,
	Grant Likely <grant.likely@...aro.org>,
	Arnd Bergmann <arnd@...db.de>,
	Linus Walleij <linus.walleij@...aro.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] of: add vendor prefix for Microchip Technology Inc

On Thursday 22 August 2013 at 09:52:49, Florian Fainelli wrote:
> Hello,
> 
> 2013/8/22 Lars Poeschel <poeschel@...onage.de>:
> > 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. ;-)
> 
> We have recently had an interesting debate for the Broadcom vendor
> prefix, so in light of this debate, I would go for the full name
> directly and use "microchip". That said, this does not necessarily
> mean that drivers containing "mcp" in their files/filenames must also
> be renamed.

Ok, I'll provide a little patch series doing it that way.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/