From: Ralph Blach <rcblach@raleigh.ibm.com>
To: Embedded Linux list <linuxppc-embedded@lists.linuxppc.org>
Subject: which errno should I use
Date: Tue, 30 Jan 2001 11:52:51 -0500 [thread overview]
Message-ID: <3A76F163.406CBFDB@raleigh.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 244 bytes --]
I am writing a character device driver. I want this device driver to
return an error if the user request less than say 1024 byte of data.
What errno should I use? Is it legal to return an error if not enouth
bytes are requested?
Thanks
Chip
[-- Attachment #2: Card for Ralph Blach --]
[-- Type: text/x-vcard, Size: 247 bytes --]
begin:vcard
n:Blach;Ralph
tel;work:919-543-1207
x-mozilla-html:TRUE
url:www.ibm.com
org:IBM MicroElectronics
adr:;;3039 Cornwallis ;RTP;NC;27709;USA
version:2.1
email;internet:rcblach@raleigh.ibm.com
x-mozilla-cpt:;15936
fn:Ralph Blach
end:vcard
next reply other threads:[~2001-01-30 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 16:52 Ralph Blach [this message]
2001-01-30 17:19 ` which errno should I use Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2001-01-31 18:48 Ian Abbott
2001-01-31 23:45 ` Ron Bianco
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=3A76F163.406CBFDB@raleigh.ibm.com \
--to=rcblach@raleigh.ibm.com \
--cc=linuxppc-embedded@lists.linuxppc.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).