From: Jim Nelson <james4765@verizon.net>
To: Edward Falk <efalk@google.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE ioctl documentation & a new ioctl
Date: Thu, 18 Nov 2004 22:47:15 -0500 [thread overview]
Message-ID: <419D6CC3.4030308@verizon.net> (raw)
In-Reply-To: <419D5CE6.8030503@google.com>
Edward Falk wrote:
> Hi all; let me introduce myself: I'm the guy that does IDE sustaining
> for Google.
>
> I'm getting ready to sit down and document the IDE ioctls. Probably
> Documentation/hdio.txt or something like that. Before I start though,
> is anybody already doing this?
>
No one that I know of. I had a thought in the back of my head of tackling ioctl
documentation after I went through the stuff that's already in Documentation, but
I figured I had enough to chew on for right now.
I'd probably make a subdirectory - i. e. Documentation/ioctl/hdio.txt - to
differentiate it from other documents, and make it easier to get maintainers to
put some stuff in there. ;) AFAICT, there is next to no documentation on ioctl's
anywhere in the kernel tarball.
> And while I'm on the subject, we're getting ready to write a new hdio
> ioctl, an extension of HDIO_DRIVE_CMD. The intent here is to be
> slightly more general-purpose than HDIO_DRIVE_CMD, with an eye to
> supporting the full set of SMART functionality. Current plan is to have
> the user pass a struct containing a pointer to the argument list, a
> pointer to the data buffer, and a data buffer length value. Consider
> this a design document; any comments and/or feature requests?
>
> -ed falk
> efalk@google.com
> -
next prev parent reply other threads:[~2004-11-19 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-19 2:39 IDE ioctl documentation & a new ioctl Edward Falk
2004-11-19 3:47 ` Jim Nelson [this message]
2004-11-19 19:38 ` Edward Falk
2004-11-19 4:07 ` Jeff Garzik
2004-11-19 19:38 ` Edward Falk
2004-11-19 20:02 ` Bartlomiej Zolnierkiewicz
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=419D6CC3.4030308@verizon.net \
--to=james4765@verizon.net \
--cc=efalk@google.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