linux-kernel - Re: [PATCH v9] Regulator: Add Anatop regulator driver

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]

Message-ID: <20120307162821.GP3107@opensource.wolfsonmicro.com>
Date:	Wed, 7 Mar 2012 16:28:22 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>
Cc:	"Ying-Chun Liu (PaulLiu)" <paul.liu@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, linaro-dev@...ts.linaro.org,
	Samuel Ortiz <sameo@...ux.intel.com>, patches@...aro.org,
	linux-kernel@...r.kernel.org, Liam Girdwood <lrg@...com>,
	Nancy Chen <Nancy.Chen@...escale.com>
Subject: Re: [PATCH v9] Regulator: Add Anatop regulator driver

On Wed, Mar 07, 2012 at 04:36:22PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:

> > This really doesn't seem at all sane for a device which is already
> > vendor specific, it's just noise in the bindings.

> No it's

...?

> Here is a good example as we have regulator generic binding & vendor
> specific bindig

It's not vendor specific, it's device specific and people are doing it
even for devices with no generic bindings at all which is particularly
silly.

Device specific prefixes probably make sense, but vendor specific ones
are just noise.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)