From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Lukas Jelinek <info@kernel-api.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel API Reference Documentation
Date: Tue, 27 Jun 2006 13:22:26 -0700 [thread overview]
Message-ID: <20060627132226.2401598e.rdunlap@xenotime.net> (raw)
In-Reply-To: <44A1858B.9080102@kernel-api.org>
On Tue, 27 Jun 2006 21:22:51 +0200 Lukas Jelinek wrote:
> 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).
FYI, there are already some kernel-doc rules in
Documentation/kernel-doc-nano-HOWTO.txt. These rules work with the
doc. generator in the kernel tree (scripts/kernel-doc).
Do you have suggestions for how to make them (the rules) better?
so that the in-tree kernel doc. will improve...
Q2: what do I get when I download one of the tarballs from kernel-api.org?
Q3: Can we see your sed scripts?
Thanks,
---
~Randy
next prev parent reply other threads:[~2006-06-27 20:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 19:22 Lukas Jelinek
2006-06-27 20:22 ` Randy.Dunlap [this message]
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=20060627132226.2401598e.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=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
all inboxes | Powered by JetHome®