From: Lukas Jelinek <info@kernel-api.org>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: ptesarik@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Kernel API Reference Documentation
Date: Wed, 28 Jun 2006 19:49:36 +0200 [thread overview]
Message-ID: <44A2C130.7060904@kernel-api.org> (raw)
In-Reply-To: <20060628095045.7522ec7f.rdunlap@xenotime.net>
>
>
> OK, I believed Petr when he stated that, I just wanted to get my
> head screwed on straight. So its the blank line between
>
> */
> and
> struct sk_buff {
> ?
Exactly.
>
> I don't think the kernel-doc rules cover that case, but
> scripts/kernel-doc handles it, so the Doxygen parser should handle
> it IMO.
>
Doxygen should handle it but doesn't do so.
Lukas
prev parent reply other threads:[~2006-06-28 17:49 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
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 [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=44A2C130.7060904@kernel-api.org \
--to=info@kernel-api.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ptesarik@suse.cz \
--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