linux-kernel - Re: 3.13-rc1: MMC & fixed regulator regression

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: <20131126210433.GG24645@blackmetal.musicnaut.iki.fi>
Date:	Tue, 26 Nov 2013 23:04:34 +0200
From:	Aaro Koskinen <aaro.koskinen@....fi>
To:	Chris Ball <cjb@...top.org>,
	Laxman Dewangan <ldewangan@...dia.com>,
	Mark Brown <broonie@...aro.org>
Cc:	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: 3.13-rc1: MMC & fixed regulator regression

Hi,

On Tue, Nov 26, 2013 at 08:03:26PM +0200, Aaro Koskinen wrote:
> On N950 with fixed vmmc regulator, MMC probe started to fail with
> 3.13-rc1:
> 
> [    2.497406] mmc0: host doesn't support card's voltages
> [    2.502899] mmc0: error -22 whilst initialising MMC card
> 
> I bisected this to c368e5fc2a190923b786f2de3e79430ea3566a25
> (regulator: fixed: get rid of {get|list}_voltage()). With this commit
> regulator_list_voltage() does not work anymore for a fixed regulator. MMC
> code is using this in mmc_regulator_get_ocrmask().

This seems to be now fixed with f446043f1aa74c2d699db48ba4a7a075b88dc14d
(regulator: fixed: fix regulator_list_voltage() for regression). For
some reason, my searches missed this commit & reports on the list.

Sorry for the noise,

A.
--
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/