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: <20121213085944.GH27624@opensource.wolfsonmicro.com>
Date:	Thu, 13 Dec 2012 08:59:44 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Marek Szyprowski <m.szyprowski@...sung.com>
Cc:	Axel Lin <axel.lin@...ics.com>, Pawel Moll <pawel.moll@....com>,
	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org,
	Chris Ball <cjb@...top.org>, Kevin Liu <keyuan.liu@...il.com>
Subject: Re: [PATCH RFC/RFT] regulator: core: Fix continuous_voltage_range
	case in regulator_can_change_voltage

On Thu, Dec 13, 2012 at 09:56:25AM +0100, Marek Szyprowski wrote:

> This change looks reasonable, I've missed the fact that there is a
> support for regulators with continuous voltage range. This change also
> shows that the n_voltages based workaround used earlier by mmc core was
> indeed only a hack and regulator_can_change_voltage() approach is much
> cleaner 

Both changes are new for v3.8 so it's not surprising that you missed the
continuous regulators.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ