From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: "Darrick J. Wong" <darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ioctl manpages?
Date: Tue, 15 Dec 2015 12:53:26 +0100 [thread overview]
Message-ID: <566FFF36.4060103@gmail.com> (raw)
In-Reply-To: <20151215083358.GE10584-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
Hello Darrick,
On 12/15/2015 09:33 AM, Darrick J. Wong wrote:
> Hi,
>
> Just out of curiosity, how does one submit manpages for specific
> ioctls? There's a manpage for ioctl() itself, but I can't find
> anything for things like, say, FIEMAP or FICLONE or FICLONERANGE.
> I guess they'd be section 2, right?
Yes. (And it sure would be nice to see some of those documented.
Is this an offer? :-) )
> Something like /usr/share/man/man2/ficlone.2.gz? Or a separate
> ioctl-ficlone.2.gz, just in case there's ever a ficlone syscall?
We already have ioctl_fat.2 and ioctl_list.2, so I'd say
ioctl_ficlone.2 and so on.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2015-12-15 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 8:33 ioctl manpages? Darrick J. Wong
[not found] ` <20151215083358.GE10584-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2015-12-15 11:53 ` Michael Kerrisk (man-pages) [this message]
[not found] ` <566FFF36.4060103-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-15 20:48 ` Darrick J. Wong
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=566FFF36.4060103@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org \
--cc=linux-api-u79uwXL29TY76Z2rM5mHXA@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).