From: Erik Mouw <J.A.K.Mouw@its.tudelft.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@suse.cz>, Andi Kleen <ak@suse.de>,
jt@hpl.hp.com, Mikael Pettersson <mikpe@csd.uu.se>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
discuss@x86-64.org
Subject: Re: two x86_64 fixes for 2.4.21-pre3
Date: Fri, 7 Feb 2003 23:58:17 +0100 [thread overview]
Message-ID: <20030207225816.GD1879@arthur.ubicom.tudelft.nl> (raw)
In-Reply-To: <1044628339.14350.5.camel@irongate.swansea.linux.org.uk>
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
On Fri, Feb 07, 2003 at 02:32:20PM +0000, Alan Cox wrote:
> -ENOSYS is the normal return for an unknown syscall. -ENOTTY for an
> invalid ioctl (-EINVAL I think is wrong ?)
About a year ago -ENOTTY was explained like this:
IOW, "not a tty" used to mean "WTF are you using ioctls here?"
- Al Viro explaining ENOTTY on linux-kernel
(Hey, the kernelnewbies.org fortunes file is useful, right? ;)
Erik
--
J.A.K. (Erik) Mouw
Email: J.A.K.Mouw@its.tudelft.nl mouw@nl.linux.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-07 22:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-24 19:16 two x86_64 fixes for 2.4.21-pre3 Mikael Pettersson
2003-01-24 19:37 ` Andi Kleen
2003-01-28 20:51 ` Mikael Pettersson
2003-01-28 21:27 ` Andi Kleen
2003-01-29 15:39 ` Mikael Pettersson
2003-01-29 16:28 ` Andi Kleen
2003-02-03 19:17 ` Mikael Pettersson
2003-02-03 19:49 ` Jean Tourrilhes
2003-02-03 20:12 ` Andi Kleen
2003-02-03 21:43 ` Jean Tourrilhes
2003-02-03 22:46 ` 32bit emulation of wireless ioctls Andi Kleen
2003-02-03 23:17 ` Jean Tourrilhes
2003-02-03 23:51 ` Andi Kleen
2003-02-04 0:09 ` Jean Tourrilhes
2003-02-03 23:58 ` David Woodhouse
2003-02-04 0:04 ` David Mosberger
2003-02-04 0:11 ` Anton Blanchard
2003-02-07 10:58 ` two x86_64 fixes for 2.4.21-pre3 Pavel Machek
2003-02-07 14:32 ` Alan Cox
2003-02-07 22:58 ` Erik Mouw [this message]
2003-02-04 3:13 ` Ton Hospel
2003-02-04 13:11 ` Mikael Pettersson
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=20030207225816.GD1879@arthur.ubicom.tudelft.nl \
--to=j.a.k.mouw@its.tudelft.nl \
--cc=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=discuss@x86-64.org \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=pavel@suse.cz \
/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).