Re: [PATCH] mmc: core: properly init drv_type

2017-12-05 Thread Ulf Hansson
On 30 November 2017 at 15:49, Wolfram Sang wrote: > When the latest version of parsing the new eMMC bindings was moved from > core.c to mmc.c, it was overlooked that drv_type could be used > uninitialized. Fix it! > > Fixes: 6186d06c519e21 ("mmc: parse new

Re: [PATCH] mmc: core: properly init drv_type

2017-12-04 Thread Simon Horman
On Mon, Dec 04, 2017 at 09:50:45AM +0100, Wolfram Sang wrote: > On Mon, Dec 04, 2017 at 09:31:13AM +0100, Geert Uytterhoeven wrote: > > Hi Wolfram, > > > > On Thu, Nov 30, 2017 at 3:49 PM, Wolfram Sang > > wrote: > > > When the latest version of parsing the new

Re: [PATCH] mmc: core: properly init drv_type

2017-12-04 Thread Wolfram Sang
On Mon, Dec 04, 2017 at 09:31:13AM +0100, Geert Uytterhoeven wrote: > Hi Wolfram, > > On Thu, Nov 30, 2017 at 3:49 PM, Wolfram Sang > wrote: > > When the latest version of parsing the new eMMC bindings was moved from > > core.c to mmc.c, it was overlooked that

Re: [PATCH] mmc: core: properly init drv_type

2017-12-04 Thread Geert Uytterhoeven
Hi Wolfram, On Thu, Nov 30, 2017 at 3:49 PM, Wolfram Sang wrote: > When the latest version of parsing the new eMMC bindings was moved from > core.c to mmc.c, it was overlooked that drv_type could be used > uninitialized. Fix it! > > Fixes: 6186d06c519e21 ("mmc:

[PATCH] mmc: core: properly init drv_type

2017-11-30 Thread Wolfram Sang
When the latest version of parsing the new eMMC bindings was moved from core.c to mmc.c, it was overlooked that drv_type could be used uninitialized. Fix it! Fixes: 6186d06c519e21 ("mmc: parse new binding for eMMC fixed driver type") Reported-by: Colin Ian King