linux-kernel - Re: [PATCH] regulator: Fix recursive mutex lockdep warning

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: <20120703224316.GB11368@opensource.wolfsonmicro.com>
Date:	Tue, 3 Jul 2012 23:43:16 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Stephen Boyd <sboyd@...eaurora.org>
Cc:	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator: Fix recursive mutex lockdep warning

On Tue, Jul 03, 2012 at 01:08:46PM -0700, Stephen Boyd wrote:
> On 07/03/12 12:26, Mark Brown wrote:

> > Applied, thanks.  Though we should probably just remove the optimal mode
> > stuff on account of the total absence of any users...

> Please don't remove it. We use the optimal stuff fairly often
> internally, plus our usb driver is upstream and using the API.

>From what I remember there's a fair bit of non-upstream code you guys
have for regulators...  your usage is certainly very unusual.

> What do you think about removing the locking in get_voltage? Is that better?

There's already an unlocked version of get_voltage()?
--
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/