From: Greg KH <gregkh@linuxfoundation.org>
To: Hartley Sweeten <HartleyS@visionengravers.com>
Cc: Chase Southwood <chase.southwood@yahoo.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"abbotti@mev.co.uk" <abbotti@mev.co.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4] Staging: comedi: convert while loop to timeout in ni_mio_common.c
Date: Wed, 15 Jan 2014 18:30:40 -0800 [thread overview]
Message-ID: <20140116023040.GB31275@kroah.com> (raw)
In-Reply-To: <DC148C5AA1CEBA4E87973D432B1C2D8817E79783@P3PWEX4MB008.ex4.secureserver.net>
On Wed, Jan 15, 2014 at 06:29:21PM +0000, Hartley Sweeten wrote:
> On Tuesday, January 14, 2014 8:59 PM, Greg KH wrote:
> > Sleep for at least 10, as I think that's the smallest time delay you can
> > sleep for anyway (meaning it will be that long no matter what number you
> > put there less than 10, depending on the hardware used of course.)
>
> A bit off topic here but I have a somewhat related question about timeouts.
>
> There are a number of comedi drivers that do a "wait for end-of-conversion"
> as part of the (*insn_read) for an analog input subdevice or (*insn_write) for
> an analog output subdevice. These functions return an errno if a timeout occurs.
>
> Currently either -ETIME or -ETIMEDOUT is returned. This errno ends up getting
> returned to the user as the result of the unlocked_ioctl file operation. What is
> the more appropriate errno? Or is there is better one that should be used?
I think they should all be -ETIMEDOUT, -ETIME is used for something
else, and shouldn't be sent to userspace as I don't think it knows what
to do with it.
thanks,
greg k-h
next prev parent reply other threads:[~2014-01-16 2:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 3:13 [PATCH] Staging: comedi: move trailing statement to next line in ni_mio_common.c Chase Southwood
2014-01-14 3:16 ` Joe Perches
2014-01-14 7:23 ` Dan Carpenter
2014-01-14 11:45 ` Ian Abbott
2014-01-14 11:48 ` Ian Abbott
2014-01-14 19:38 ` [PATCH v2] Staging: comedi: convert while loop to timeout " Chase Southwood
2014-01-14 19:45 ` Joe Perches
2014-01-14 19:50 ` Greg KH
2014-01-14 21:31 ` [PATCH v3] " Chase Southwood
2014-01-14 23:10 ` Greg KH
2014-01-15 0:23 ` [PATCH v4] " Chase Southwood
2014-01-15 3:58 ` Greg KH
2014-01-15 10:29 ` Ian Abbott
2014-01-15 18:29 ` Hartley Sweeten
2014-01-16 2:30 ` Greg KH [this message]
2014-01-16 11:08 ` Ian Abbott
2014-01-15 5:15 ` [PATCH v5] " Chase Southwood
2014-01-15 10:38 ` Ian Abbott
2014-01-15 17:51 ` [PATCH v6] " Chase Southwood
2014-01-15 18:48 ` Hartley Sweeten
2014-01-15 19:22 ` [PATCH v7] " Chase Southwood
2014-01-16 11:30 ` Ian Abbott
2014-01-16 17:46 ` Chase Southwood
2014-01-16 18:27 ` [PATCH v8] " Chase Southwood
2014-01-17 13:12 ` Ian Abbott
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=20140116023040.GB31275@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=HartleyS@visionengravers.com \
--cc=abbotti@mev.co.uk \
--cc=chase.southwood@yahoo.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-kernel@vger.kernel.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