Re: [PATCH 01/17] mmc: core: shut up "voltage-ranges unspecified" pr_info()

On Mon, Dec 21, 2015 at 11:18:15AM +0100, Ulf Hansson wrote: > On 19 December 2015 at 21:29, Russell King > wrote: > > Each time a driver such as sdhci-esdhc-imx is probed, we get a info > > printk complaining that the DT voltage-ranges property has not been > >

Re: [PATCH 01/17] mmc: core: shut up "voltage-ranges unspecified" pr_info()

On 19 December 2015 at 21:29, Russell King wrote: > Each time a driver such as sdhci-esdhc-imx is probed, we get a info > printk complaining that the DT voltage-ranges property has not been > specified. > > However, the DT binding specifically says that the

[PATCH 01/17] mmc: core: shut up "voltage-ranges unspecified" pr_info()

Each time a driver such as sdhci-esdhc-imx is probed, we get a info printk complaining that the DT voltage-ranges property has not been specified. However, the DT binding specifically says that the voltage-ranges property is optional. That means we should not be complaining that DT hasn't

[PATCH 01/17] mmc: core: shut up "voltage-ranges unspecified" pr_info()

Each time a driver such as sdhci-esdhc-imx is probed, we get a info printk complaining that the DT voltage-ranges property has not been specified. However, the DT binding specifically says that the voltage-ranges property is optional. That means we should not be complaining that DT hasn't