linux-kernel - Re: [PATCH V2 0/3] regulator: dt: add policy to match regulator with prop "regulator-compatible"

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20120621095304.GN4037@opensource.wolfsonmicro.com>
Date:	Thu, 21 Jun 2012 10:53:04 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	Laxman Dewangan <ldewangan@...dia.com>,
	devicetree-discuss@...ts.ozlabs.org, grant.likely@...retlab.ca,
	rob.herring@...xeda.com, arnd@...db.de, lrg@...com,
	lee.jones@...aro.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 0/3] regulator: dt: add policy to match regulator with
 prop "regulator-compatible"

On Wed, Jun 20, 2012 at 10:23:52AM -0600, Stephen Warren wrote:

> Related to this, I wonder if we need some scheme to tag individual
> bindings as under-development vs. final, and some way to promote
> bindings between those states (a bindings review board?!). Do binding

Part of the trouble with this, and the reason why it doesn't really work
for sysfs, is that people generally don't think there's a problem with
the bindings until they run into it or until someone new comes along and
reviews them.  Apart from the OMAP hwmod thing generally we aren't doing
anything that's not supposed to last.

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