On 14/02/16 23:09, Matt Ranostay wrote: > Jonathan et all, > > Has anyone noticed that there is no clear consensus on which error > code to return when a i2c_check_functionality() check fails within the > probe function. I've seen so far ENODEV, ENOTSUPP, EOPNOTSUPP, EIO, > and ENOSYS in drivers/iio > > Shouldn't these be made a standard value like -ENOTSUPP? Would make sense - but is this the right choice. Thought I'd grep HWMON as a possible source of a consensus on this and got no clear answer. The most common in there looks to be -ENODEV though (From the first few pages of results anyway ;) Hohum. Wolfram what do you think? Worth cleaning this up? Perhaps even kernel wise would lead to some consistency. I've never been that sharp on this in IIO so I can't really talk ;) Jonathan > > Thanks, > > Matt > -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
