From: corbet-lk@lwn.net (Jonathan Corbet)
To: linux-kernel@vger.kernel.org
Cc: Steven_Snyder@3com.com
Subject: Re: Current doc for writing device drivers?
Date: Mon, 13 Nov 2000 16:11:04 -0700 [thread overview]
Message-ID: <20001113231104.13349.qmail@eklektix.com> (raw)
In-Reply-To: Your message of "Mon, 13 Nov 2000 10:53:30 EST." <3A100E7A.2F00682E@mandrakesoft.com>
> The Rubini book is being updated for 2.2 and 2.4, but I dunno when it
> will go to press.
We're working on it - honest!
The book will go out for technical review before too long; I believe the
current target date to have it on the shelves is April. We'd hoped for
sooner, but, given how 2.4 development has gone, I think the timing is
about right. After all, we wouldn't want to present the wrong prototype
for kmap() or miss out on the new inter-module communication API...:)
jon
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-11-13 23:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-13 15:49 Current doc for writing device drivers? Steven_Snyder
2000-11-13 15:53 ` Jeff Garzik
2000-11-13 23:11 ` Jonathan Corbet [this message]
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=20001113231104.13349.qmail@eklektix.com \
--to=corbet-lk@lwn.net \
--cc=Steven_Snyder@3com.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