linux-kernel - Re: [RFC v1] regulator: core: introduce regulator chain locking scheme

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: <20130415164018.GA14064@sirena.org.uk>
Date:	Mon, 15 Apr 2013 17:40:18 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Andrii Tseglytskyi <andrii.tseglytskyi@...com>
Cc:	Mark Brown <broonie@...nel.org>,
	Grygorii Strashko <grygorii.strashko@...com>,
	Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
	linux-kernel@...r.kernel.org,
	Mike Turquette <mturquette@...aro.org>,
	Nishanth Menon <nm@...com>, Tero Kristo <t-kristo@...com>,
	linux-omap <linux-omap@...r.kernel.org>,
	linux-arm <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC v1] regulator: core: introduce regulator chain locking
 scheme

On Mon, Apr 15, 2013 at 07:21:25PM +0300, Andrii Tseglytskyi wrote:
> On 04/15/2013 06:50 PM, Mark Brown wrote:

> >>In addition, such locking scheme allows to have access to the supplier
> >>regulator API from inside child's (consumer) regulator API.

> >I've still not seen any use case articulated for doing this...

> Use case is introduced in ABB series:

Sorry, I meant any sensible use case.
--
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/