From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Antti Palosaari <crope@iki.fi>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: suitable IOCTL error code when device is in state IOCTL cannot performed
Date: Sun, 12 Aug 2012 14:48:43 -0300 [thread overview]
Message-ID: <5027EC7B.5010009@redhat.com> (raw)
In-Reply-To: <5027DC16.8050604@iki.fi>
Em 12-08-2012 13:38, Antti Palosaari escreveu:
> Subject says it all. Which one error value is most suitable / generic ?
>
> Here are few ones I found which could be possible:
>
> #define EPERM 1 /* Operation not permitted */
> #define EAGAIN 11 /* Try again */
> #define EACCES 13 /* Permission denied */
> #define EBUSY 16 /* Device or resource busy */
> #define ENODATA 61 /* No data available */
> #define ECANCELED 125 /* Operation Canceled */
IMHO, EAGAIN, EBUSY or ENODATA are the most pertinent ones.
Regards,
Mauro
prev parent reply other threads:[~2012-08-12 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-12 16:38 suitable IOCTL error code when device is in state IOCTL cannot performed Antti Palosaari
2012-08-12 17:48 ` Mauro Carvalho Chehab [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=5027EC7B.5010009@redhat.com \
--to=mchehab@redhat.com \
--cc=crope@iki.fi \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).