From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH] i2c-pca-algo: Fix errorcode
Date: Tue, 20 May 2008 21:42:07 +0200 [thread overview]
Message-ID: <20080520194206.GA11088@pengutronix.de> (raw)
In-Reply-To: <20080520201755.59b140f5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 748 bytes --]
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
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
prev parent reply other threads:[~2008-05-20 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 17:18 [PATCH] i2c-pca-algo: Fix errorcode Wolfram Sang
[not found] ` <20080520171848.10908.23451.stgit-WosDo8ZsKtpoC+DoxizDebTfikLOBL9CDsAVuJBuCrE@public.gmane.org>
2008-05-20 18:17 ` Jean Delvare
[not found] ` <20080520201755.59b140f5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-05-20 19:42 ` Wolfram Sang [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080520194206.GA11088@pengutronix.de \
--to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox