From: Oliver Neukum <oliver@neukum.org>
To: "linux-os (Dick Johnson)" <linux-os@analogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: error to be returned while suspended
Date: Tue, 3 Oct 2006 15:02:33 +0200 [thread overview]
Message-ID: <200610031502.33545.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0610030846040.21211@chaos.analogic.com>
Am Dienstag, 3. Oktober 2006 14:51 schrieb linux-os (Dick Johnson):
>
> On Tue, 3 Oct 2006, Oliver Neukum wrote:
>
> > Hi,
> >
> > which error should a character device return if a read/write cannot be
> > serviced because the device is suspended? Shouldn't there be an error
> > code specific to that?
> >
> > Regards
> > Oliver
>
> The de-facto error codes were created long before one could "suspend"
> a device, so there isn't a ESUSP code. However, I suggest EIO or EBUSY
CUPS chokes on these. Is it acceptable to say that you should know
what you're doing when suspending?
> unless you want to define an ESUSP and get it accepted by the POSIX
> committee.
This would be the cleanest solution. How does one do that?
Regards
Oliver
next prev parent reply other threads:[~2006-10-03 13:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 11:23 error to be returned while suspended Oliver Neukum
2006-10-03 12:51 ` linux-os (Dick Johnson)
2006-10-03 13:02 ` Oliver Neukum [this message]
2006-10-03 14:17 ` linux-os (Dick Johnson)
2006-10-04 11:19 ` Pavel Machek
2006-10-04 16:34 ` Oliver Neukum
2006-10-04 22:44 ` Pavel Machek
2006-10-05 7:07 ` Oliver Neukum
2006-10-05 8:57 ` Pavel Machek
2006-10-05 16:21 ` [linux-usb-devel] " Alan Stern
2006-10-05 16:35 ` Oliver Neukum
2006-10-05 18:24 ` Alan Stern
2006-10-05 18:43 ` Oliver Neukum
2006-10-05 20:48 ` Alan Stern
2006-10-05 21:25 ` Oliver Neukum
2006-10-05 21:45 ` Alan Stern
2006-10-06 7:21 ` Oliver Neukum
2006-10-06 17:48 ` Alan Stern
2006-10-06 11:25 ` Pavel Machek
2006-10-06 2:47 ` David Brownell
2006-10-06 7:04 ` Oliver Neukum
2006-10-06 11:27 ` Pavel Machek
2006-10-06 14:09 ` Oliver Neukum
2006-10-06 21:10 ` David Brownell
2006-10-07 10:49 ` Oliver Neukum
2006-10-07 11:08 ` Pavel Machek
2006-10-07 17:16 ` Oliver Neukum
2006-10-08 0:03 ` David Brownell
2006-10-08 2:03 ` Alan Stern
2006-10-08 7:07 ` Oliver Neukum
2006-10-08 14:27 ` Alan Stern
2006-10-08 19:36 ` Pavel Machek
2006-10-08 19:57 ` Oliver Neukum
2006-10-08 21:06 ` Pavel Machek
2006-10-08 6:40 ` Oliver Neukum
2006-10-09 15:56 ` David Brownell
2006-10-08 6:51 ` Oliver Neukum
2006-10-08 7:14 ` Oliver Neukum
2006-10-08 13:24 ` Oliver Neukum
2006-10-08 14:32 ` Alan Stern
2006-10-08 19:41 ` /sys/.../power/state " Pavel Machek
2006-10-08 19:19 ` Pavel Machek
[not found] ` <200610080838.03488.oliver@neukum.org>
[not found] ` <200610080020.49158.david-b@pacbell.net>
2006-10-08 8:39 ` Oliver Neukum
2006-10-08 14:16 ` Dmitry Torokhov
2006-10-06 11:23 ` Pavel Machek
2006-10-06 11:21 ` Pavel Machek
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=200610031502.33545.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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