From: Sam Clegg <sam-vp0mx6+5gkqFX2APIN6yfw@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [patch] Change the name of first ioctl arg to 'fd'.
Date: Mon, 05 Aug 2013 12:36:47 -0700 [thread overview]
Message-ID: <51FFFECF.3000500@superduper.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 108 bytes --]
I noticed this inconsistency between the ioctl man pages and the pages
for all other FD accepting syscalls.
[-- Attachment #2: 0001-Change-the-name-of-first-ioctl-arg-from-d-to-fd.patch --]
[-- Type: text/x-patch, Size: 1041 bytes --]
diff --git a/man2/ioctl.2 b/man2/ioctl.2
index 3d7a11c..d00e71a 100644
--- a/man2/ioctl.2
+++ b/man2/ioctl.2
@@ -44,7 +44,7 @@ ioctl \- control device
.SH SYNOPSIS
.B #include <sys/ioctl.h>
.sp
-.BI "int ioctl(int " d ", int " request ", ...);"
+.BI "int ioctl(int " fd ", int " request ", ...);"
.SH DESCRIPTION
The
.BR ioctl ()
@@ -54,7 +54,7 @@ In particular, many operating characteristics of character special files
.BR ioctl ()
requests.
The argument
-.I d
+.I fd
must be an open file descriptor.
.PP
The second argument is a device-dependent request code.
@@ -92,8 +92,8 @@ is set appropriately.
.SH ERRORS
.TP 0.7i
.B EBADF
-.I d
-is not a valid descriptor.
+.I fd
+is not a valid file descriptor.
.TP
.B EFAULT
.I argp
@@ -106,13 +106,13 @@ or
is not valid.
.TP
.B ENOTTY
-.I d
+.I fd
is not associated with a character special device.
.TP
.B ENOTTY
The specified request does not apply to the kind of object that the
descriptor
-.I d
+.I fd
references.
.SH CONFORMING TO
No single standard.
--
1.8.3
reply other threads:[~2013-08-05 19:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51FFFECF.3000500@superduper.net \
--to=sam-vp0mx6+5gkqfx2apin6yfw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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).