From: Lukas Jelinek <info@kernel-api.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel API Reference Documentation
Date: Tue, 27 Jun 2006 22:42:20 +0200 [thread overview]
Message-ID: <44A1982C.1010008@kernel-api.org> (raw)
In-Reply-To: <20060627132226.2401598e.rdunlap@xenotime.net>
>
> 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...
These rules seem to be good. I will try to use the generator
(scripts/kernel-doc) and check the result.
But the bigger problem is that many headers are not documented at all.
And some code is documented but not complying the rules.
>
> Q2: what do I get when I download one of the tarballs from kernel-api.org?
>
Each tarball contains exactly the same as can be browsed online at
kernel-api.org. There is no difference.
> Q3: Can we see your sed scripts?
>
Yes, here it is (it's really small and mindless):
--- sed script begin ---
/^\(\s\)*#endif/ {
s/\/\*/\/\//
s/\*\///
}
/^\(\s\)*\/\*.*\*\/\(\s\)*$/ {
s/\/\*/\/\/\//
s/\*\///
}
/^.*\/\*.*\*\/\(\s\)*$/ {
s/\/\*/\/\/\/</
s/\*\///
}
s/^\(\s\)*\/\*/\/\*\*\n/
s/^.*\*\//\n\*\//
--- sed script end ---
next prev parent reply other threads:[~2006-06-27 20:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 19:22 Kernel API Reference Documentation Lukas Jelinek
2006-06-27 20:22 ` Randy.Dunlap
2006-06-27 20:42 ` Lukas Jelinek [this message]
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=44A1982C.1010008@kernel-api.org \
--to=info@kernel-api.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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