> >-if (ret < 0)
> >+if (ret < 0 && ret != -EREMOTEIO)
> > dev_err(dev, "error %d : %x\n", ret, priv->flags);
>
>Hm, I'm now getting -EBUSY and -EAGAIN running i2cdetect on
> R8A7791 base Henninger board. Only when I comment out the above 2
> lines, I can get the bus scann
Hello.
On 01/26/2014 07:05 PM, Ben Dooks wrote:
The i2c-rcar driver currently prints an error message if the master_xfer
callback fails. However if the bus is being probed then lots of NAKs
will be generated, causing the output of a number of errors printed.
To solve this, disable the print
On Thu, May 08, 2014 at 04:46:51PM +0200, Arnd Bergmann wrote:
> These are a bunch of fixes I had to do to get all randconfig
> configurations on ARM working. Most of these are really old
> bugs, but there are also some new ones. I don't think any of
> them require a backport to linux-stable.
>
>
As far as I can tell, this driver must have produced this error
for as long as it has been merged into the mainline kernel, but
it was never part of the normal build tests:
drivers/i2c/busses/i2c-nuc900.c: In function 'nuc900_i2c_probe':
drivers/i2c/busses/i2c-nuc900.c:601:17: error: request for m
These are a bunch of fixes I had to do to get all randconfig
configurations on ARM working. Most of these are really old
bugs, but there are also some new ones. I don't think any of
them require a backport to linux-stable.
I have checked that they are all still required on yesterday's
linux-next k
