linux-kernel - Re: [PATCH] Regulator: Reorder the min max assignment in the sequence of regulator_set

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: <20130208112848.GM8879@opensource.wolfsonmicro.com>
Date:	Fri, 8 Feb 2013 11:28:48 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	J Keerthy <j-keerthy@...com>
Cc:	linux-kernel@...r.kernel.org, lgirdwood@...il.com
Subject: Re: [PATCH] Regulator: Reorder the min max assignment in the
 sequence of regulator_set_voltage function

On Fri, Feb 01, 2013 at 10:34:58AM +0530, J Keerthy wrote:

> +++ b/drivers/regulator/core.c
> @@ -81,6 +81,8 @@ struct regulator {
>  	int uA_load;
>  	int min_uV;
>  	int max_uV;
> +	int curr_min_uV;
> +	int curr_max_uV;

This change makes sense but I don't see why we need to add these to
struct regulator - why not just store the values locally for unwinding?

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