linux-kernel - Re: [PATCH v3] regulator: ad5398: Fix min/max current limit boundary checking

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: <20120704113942.GR4111@opensource.wolfsonmicro.com>
Date:	Wed, 4 Jul 2012 12:39:42 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Axel Lin <axel.lin@...il.com>
Cc:	linux-kernel@...r.kernel.org, Sonic Zhang <sonic.zhang@...log.com>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Liam Girdwood <lrg@...com>
Subject: Re: [PATCH v3] regulator: ad5398: Fix min/max current limit boundary
 checking

On Wed, Jul 04, 2012 at 11:55:07AM +0800, Axel Lin wrote:
> It is ok to request current limit with min_uA < chip->min_uA and
> max_uA > chip->max_uA.

Applied, thanks.

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