Hi Uwe,
On Wed, Jul 11, 2012 at 01:36:48PM +0200, Uwe Kleine-König wrote:
> This was introduced in commit
>
> 876989d (mfd: Add device tree probe support for mc13xxx)
>
> for spi and later while introducing support for i2c copied to the i2c
> driver.
>
> Modifying driver details is very
Hi Uwe,
On Wed, Jul 11, 2012 at 01:36:48PM +0200, Uwe Kleine-König wrote:
This was introduced in commit
876989d (mfd: Add device tree probe support for mc13xxx)
for spi and later while introducing support for i2c copied to the i2c
driver.
Modifying driver details is very strange,
On Wed, Jul 11, 2012 at 01:36:48PM +0200, Uwe Kleine-König wrote:
> This was introduced in commit
>
> 876989d (mfd: Add device tree probe support for mc13xxx)
>
> for spi and later while introducing support for i2c copied to the i2c
> driver.
>
> Modifying driver details is very strange,
This was introduced in commit
876989d (mfd: Add device tree probe support for mc13xxx)
for spi and later while introducing support for i2c copied to the i2c
driver.
Modifying driver details is very strange, for example probing an
mc13892 device (instantiated via dt) removes the driver's
This was introduced in commit
876989d (mfd: Add device tree probe support for mc13xxx)
for spi and later while introducing support for i2c copied to the i2c
driver.
Modifying driver details is very strange, for example probing an
mc13892 device (instantiated via dt) removes the driver's
On Wed, Jul 11, 2012 at 01:36:48PM +0200, Uwe Kleine-König wrote:
This was introduced in commit
876989d (mfd: Add device tree probe support for mc13xxx)
for spi and later while introducing support for i2c copied to the i2c
driver.
Modifying driver details is very strange, for
6 matches
Mail list logo