All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC] i2c_check_functionality and error code
@ 2016-02-14 23:09 Matt Ranostay
       [not found] ` <CAKzfze-B4dx9aghERaRDu7xz0i6pMJcAUGMQX7OWJpWh7i=bxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
  0 siblings, 1 reply; 7+ messages in thread
From: Matt Ranostay @ 2016-02-14 23:09 UTC (permalink / raw)
  To: Jonathan Cameron, linux-iio@vger.kernel.org

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?

Thanks,

Matt

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2016-02-24 20:42 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-02-14 23:09 [RFC] i2c_check_functionality and error code Matt Ranostay
     [not found] ` <CAKzfze-B4dx9aghERaRDu7xz0i6pMJcAUGMQX7OWJpWh7i=bxw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-02-21 20:33   ` Jonathan Cameron
2016-02-21 20:33     ` Jonathan Cameron
     [not found]     ` <56CA1F0D.2060707-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2016-02-21 22:56       ` Wolfram Sang
2016-02-21 22:56         ` Wolfram Sang
2016-02-24 20:42         ` Jonathan Cameron
2016-02-24 20:42           ` Jonathan Cameron

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.