From: Lukas Jelinek <info@kernel-api.org>
To: linux-kernel@vger.kernel.org
Subject: Kernel API Reference Documentation
Date: Tue, 27 Jun 2006 21:22:51 +0200 [thread overview]
Message-ID: <44A1858B.9080102@kernel-api.org> (raw)
Hello,
a few months ago I looked for something like "Linux Kernel API Reference
Documentation". This search was unsuccessful and somebody recommended me
to generate this documentation from the kernel headers.
I have used Doxygen for this work. But the headers have needed to be
preprocessed by 'sed' using some regexp rules (due to various
incompatible comment formats).
Now I decide to share the result worldwide. The current generated
"Kernel API Reference" can be found at http://www.kernel-api.org.
Although it is very buggy this time I think it may be useful for module
developers.
To allow this work to be better, I suggest to establish some rules for
writing code comments (especially for function prototypes, data
structures etc.) and to add the comments to the kernel headers. The
rules should be chosen carefully to be well accepted by various
documentation generators (at least by Doxygen).
Thank you for your time dedicated to this idea.
Regards
Lukas Jelinek
next reply other threads:[~2006-06-27 19:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 19:22 Lukas Jelinek [this message]
2006-06-27 20:22 ` Kernel API Reference Documentation Randy.Dunlap
2006-06-27 20:42 ` Lukas Jelinek
2006-06-27 21:38 ` Randy.Dunlap
2006-06-28 9:44 ` Steven Rostedt
2006-06-28 10:01 ` Andreas Schwab
2006-06-28 12:05 ` Martin Waitz
2006-06-28 12:26 ` Lukas Jelinek
2006-06-28 11:47 ` Petr Tesarik
2006-06-28 12:22 ` Lukas Jelinek
2006-06-28 16:09 ` Randy.Dunlap
2006-06-28 16:13 ` Petr Tesarik
2006-06-28 16:36 ` Randy.Dunlap
2006-06-28 16:41 ` Lukas Jelinek
2006-06-28 16:50 ` Randy.Dunlap
2006-06-28 17:49 ` Lukas Jelinek
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=44A1858B.9080102@kernel-api.org \
--to=info@kernel-api.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