From: Alexey Dobriyan <adobriyan@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [RFC] Documentation/ioctl-mess.txt format
Date: Sun, 11 Sep 2005 05:09:36 +0400 [thread overview]
Message-ID: <20050911010935.GA10781@mipter.zuzino.mipt.ru> (raw)
In-Reply-To: <20050911005342.GC32299@mipter.zuzino.mipt.ru>
Now that first two patches hit -mm (thanks, Andrew), please, comment
on:
a) Layout.
This one is a-la MAINTAINERS, CREDITS. I like it.
b) Fields for future additions.
Input and output wrt userspace are the easiest ones to extract, so
I'll do them first.
Obviously, "D: " should exist (already found some good descriptions
under GFDL, arrgh). Possibly "R: " -- return values. Following code
can be tricky and deep.
P. S.: some of you would like to see "P: " field very much, but that
would require a _lot_ of archaeology. ;-)
--- linux-ioctl-mess.txt-000/Documentation/ioctl-mess.txt
+++ linux-ioctl-mess.txt-001/Documentation/ioctl-mess.txt
@@ -7,23 +7,66 @@ time for patch-cooking, simple "there is
would also be fine.
Please, keep the list in alphabetical order.
+
+Legend
+------
+N: NAME
+I: data copied from userspace with copy_from_user(), or
+ "I: (int) arg", or
+ "I: -".
+O: data copied to userspace with copy_to_user() or put_user(), or
+ "O: -".
----------------------------------------------------------------------------
0x1260
0x41545900
0x41545901
0x4B50
0x4B51
-ADD_NEW_DISK
-AGPIOC_ACQUIRE
-AGPIOC_ALLOCATE
-AGPIOC_BIND
-AGPIOC_DEALLOCATE
-AGPIOC_INFO
-AGPIOC_PROTECT
-AGPIOC_RELEASE
-AGPIOC_RESERVE
-AGPIOC_SETUP
-AGPIOC_UNBIND
+
+N: ADD_NEW_DISK
+I: mdu_disk_info_t
+O: -
+
+N: AGPIOC_ACQUIRE
+I: -
+O: -
+
+N: AGPIOC_ALLOCATE
+I: struct agp_allocate
+O: struct agp_allocate
+
+N: AGPIOC_BIND
+I: struct agp_bind
+O: -
+
+N: AGPIOC_DEALLOCATE
+I: int (arg)
+O: -
+
+N: AGPIOC_INFO
+I: -
+O: struct agp_info
+
+N: AGPIOC_PROTECT
+I: -
+O: -
+
+N: AGPIOC_RELEASE
+I: -
+O: -
+
+N: AGPIOC_RESERVE
+I: struct agp_region [+ sizeof(struct agp_segment) * struct agp_region::seg_count)]
+O: -
+
+N: AGPIOC_SETUP
+I: struct agp_setup
+O: -
+
+N: AGPIOC_UNBIND
+I: struct agp_unbind
+O: -
+
AMDTP_IOC_ZAP
APM_IOC_STANDBY
APM_IOC_SUSPEND
parent reply other threads:[~2005-09-11 0:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050911005342.GC32299@mipter.zuzino.mipt.ru>]
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=20050911010935.GA10781@mipter.zuzino.mipt.ru \
--to=adobriyan@gmail.com \
--cc=linux-kernel@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).