linux-kernel - Re: [PATCH 1/2] regulator: Allow boot_on regulators to be disabled by clients

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: <1236166858.6781.1.camel@vega.slimlogic.co.uk>
Date:	Wed, 04 Mar 2009 11:40:58 +0000
From:	Liam Girdwood <lrg@...mlogic.co.uk>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] regulator: Allow boot_on regulators to be disabled
 by clients

On Mon, 2009-03-02 at 16:32 +0000, Mark Brown wrote:
> Rather than incrementing the reference count for boot_on regulators
> (which prevents them being disabled later on) simply force the
> regulator to be enabled when applying the constraints. Previously
> boot_on was essentially equivalent to always_on.
> 
> Signed-off-by: Mark Brown <broonie@...nsource.wolfsonmicro.com>
> ---
>  drivers/regulator/core.c          |   13 ++++---------
>  include/linux/regulator/machine.h |    4 +++-
>  2 files changed, 7 insertions(+), 10 deletions(-)

Applied.

Thanks

Liam

--
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/