linux-kernel - Re: [PATCH V2 2/3] regulator: dt: add policy to have property "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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20120619180647.GP3974@opensource.wolfsonmicro.com>
Date:	Tue, 19 Jun 2012 19:06:47 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Warren <swarren@...dotorg.org>
Cc:	Laxman Dewangan <ldewangan@...dia.com>, grant.likely@...retlab.ca,
	rob.herring@...xeda.com, arnd@...db.de, linus.walleij@...aro.org,
	lrg@...com, lee.jones@...aro.org,
	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH V2 2/3] regulator: dt: add policy to have property
 "regulator-compatible"

On Tue, Jun 19, 2012 at 12:03:27PM -0600, Stephen Warren wrote:

> So while as you say regulator.txt might not mandate that this be the
> only method of handling multiple child nodes, shouldn't it document
> this method as /a/ method in a central location to avoid all the
> bindings that make use of this feature from duplicating the documentation?

Sure, but I'd expect some reference in the individual binding documents
to the mechanism being used for a given device (which seems to be what
Laxman has here).

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