linux-kernel - Re: [PATCH V2] 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]

Date:	Mon, 11 Feb 2013 17:05:25 +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 V2] Regulator: Reorder the min max assignment in the
 sequence of regulator_set_voltage function

On Mon, Feb 11, 2013 at 12:19:34PM +0530, J Keerthy wrote:

> The min and max values for regulators are getting assigned before actually
> the voltage is set. So making sure that min and max values are assigned
> only if the voltage is successfully set else keeping the last successfully
> set voltage's min and max values.

> This is boot tested on OMAP4430 and OMAP4460 boards.

This seems fine but doesn't apply against topic/core or -next, can you
please regenerate against topic/core and resend?

> V2: Fixed comment from Mark. Introduced local variables to hold current
> min and max values.

Don't include things like this in the changelog, include them after the
--- as covered in SubmittingPatches.

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