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] [day] [month] [year] [list]

Message-ID: <DC88CAD03C0052499C1907B327FC63229B95A0@DBDE01.ent.ti.com>
Date:	Mon, 11 Feb 2013 05:26:20 +0000
From:	"J, KEERTHY" <j-keerthy@...com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"lgirdwood@...il.com" <lgirdwood@...il.com>
Subject: RE: [PATCH] Regulator: Reorder the min max assignment in the
 sequence of regulator_set_voltage function

Hi Mark,

> -----Original Message-----
> From: Mark Brown [mailto:broonie@...nsource.wolfsonmicro.com]
> Sent: Friday, February 08, 2013 4:59 PM
> To: J, KEERTHY
> 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?

Ok. I will send an updated patch. Thanks for the response
And sorry for the top posting.

Regards,
Keerthy
--
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/