From: Charles Samuels <charles@kde.org>
To: linux-kernel@vger.kernel.org
Subject: Kernel Documentation
Date: Tue, 17 Jul 2001 13:24:42 -0700 [thread overview]
Message-ID: <200107172024.NAA19545@altair.dhs.org> (raw)
I apologize for using the D-word, however, I've created some, so I think that
makes it acceptable.
But first, I was having a little fun kernel-hacking the other day, and I had
noticed that every time I want information on function-X, I have to start
grepping like hell, and it's even worse when I don't know the name of the
function. What we needed was an API (KPI?) reference.
So I made one.
<blink><marquee> http://derkarl.org/kerneldoc/ </marquee></blink>
(It seems that 10% of europe can't get that domain: 207.44.242.45)
Obviously, it's not complete, in fact, if it were any less complete, I could
call it the linux kernel :)
The _real_ reason I post this message is, of course, for help. I'll be more
than happy to accept new xml documentation files (the bottom of each page
contains a link to the associated XML file, as an example).
PS. I'm not on this mailing list (I'm on plenty, don't worry), so I'll be
following it on the archives.
-Charles
next reply other threads:[~2001-07-17 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-17 20:24 Charles Samuels [this message]
2001-07-17 20:46 ` Kernel Documentation Ignacio Vazquez-Abrams
-- strict thread matches above, loose matches on Subject: below --
2001-07-17 21:02 Charles Samuels
2001-07-17 21:18 ` Crutcher Dunnavant
2001-07-17 21:25 ` Charles Samuels
2001-07-17 21:31 ` Charles Samuels
2001-07-18 2:19 ` John Levon
2001-07-18 9:06 ` Tim Jansen
2001-07-18 10:18 ` Tim Waugh
2001-07-17 21:28 ` Ignacio Vazquez-Abrams
2001-07-17 21:32 ` Crutcher Dunnavant
2001-07-17 21:28 ` Wichert Akkerman
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=200107172024.NAA19545@altair.dhs.org \
--to=charles@kde.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