| 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
| ||
|
Date: Mon, 11 Feb 2013 12:26:42 -0500 From: Chris Ball <cjb@...top.org> To: Marek Szyprowski <m.szyprowski@...sung.com> Cc: linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org, Kyungmin Park <kyungmin.park@...sung.com>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Liam Girdwood <lrg@...com>, Kevin Liu <keyuan.liu@...il.com> Subject: Re: [PATCH 2/3] mmc: use regulator_can_change_voltage() instead of regulator_count_voltages() hacks Hi Marek, On Fri, Feb 01 2013, Marek Szyprowski wrote: > On 12/4/2012 3:01 PM, Marek Szyprowski wrote: >> mmc_regulator_set_ocr() depends on the ability of regulator to change the >> voltage value. When regulator cannot change its voltage output, some code is >> skipped to avoid reporting false errors on some boards, which use MMC hosts >> with fixed regulators (example: Samsung Goni and UniversalC210 boards). >> >> This patch replaces a hacky workaround based on regulator_count_voltages() >> value with the correct call to recently introduced >> regulator_can_change_voltage() function in regulators core. >> >> Signed-off-by: Marek Szyprowski <m.szyprowski@...sung.com> > > Any chance to get this patch scheduled for v3.9? Thanks, pushed to mmc-next for 3.9. - Chris. -- Chris Ball <cjb@...top.org> <http://printf.net/> One Laptop Per Child -- 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