From: Jeff Garzik <jgarzik@pobox.com>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: libata dev guide updated
Date: Mon, 30 May 2005 20:54:35 -0400 [thread overview]
Message-ID: <429BB5CB.2020708@pobox.com> (raw)
Just made a run through the libata docs, updating them for the latest
hooks and filling in missing details like locking/context documentation.
I've been playing with lulu.com self-publishing, and published this
newly updated libata Developer's Guide there as a short book (92 pages):
http://www.lulu.com/content/130446
I think the muddy road on the front cover is apropos :)
This guide continues to be open source -- just run "make pdfdocs" in the
kernel source tree.
A PDF of the book is available for free on lulu.com or at
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata.pdf or by
running "make pdfdocs" (or "make psdocs", "make htmldocs", ...).
The source code for the guide is in the kernel source tree, with new
additions in the 'docs' branch of
rsync://rsync.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
next reply other threads:[~2005-05-31 0:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 0:54 Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-17 22:48 libata dev guide updated Jeff Garzik
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=429BB5CB.2020708@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--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).