Hi Jean, On Tue, May 20, 2008 at 08:17:55PM +0200, Jean Delvare wrote:
> EBUSY is a fatal error, while a you should be able to retry the > transaction later when the bus is free. So I think that EAGAIN would be > more appropriate. Okay, fine with me. (Does somebody know of a guide with references for using errorcodes? EBUSY or EAGAIN? ENODEV or ENXIO? Preferred error value if ioremap fails? It seems a bit messy. The patch that was recently posted, defining possible situations for errorcodes within I2C is really great. I wished I would have something like this for the general kernel-routines.) Wolfram -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry
signature.asc
Description: Digital signature
_______________________________________________ i2c mailing list [email protected] http://lists.lm-sensors.org/mailman/listinfo/i2c
