mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Tesarik <ptesarik@suse.cz>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: Lukas Jelinek <info@kernel-api.org>, linux-kernel@vger.kernel.org
Subject: Re: Kernel API Reference Documentation
Date: Wed, 28 Jun 2006 18:13:35 +0200	[thread overview]
Message-ID: <1151511215.8127.74.camel@elijah.suse.cz> (raw)
In-Reply-To: <20060628090950.c1862a9e.rdunlap@xenotime.net>

On Wed, 2006-06-28 at 09:09 -0700, Randy.Dunlap wrote:
> On Wed, 28 Jun 2006 14:22:53 +0200 Lukas Jelinek wrote:
> 
> > > I looked at
> > > http://www.kernel-api.org/docs/online/2.6.17/da/dab/structsk__buff.html
> > > 
> > > and you apparently ignore kernel-doc for structs. Cf.
> > > include/linux/skbuff.h:177 ff.
> > 
> > There are several problems. The one you describe is probably caused by a
> > blank line between the struct and the related comment. Doxygen doesn't
> > recognize it correctly (and simply ignores the comment).
> 
> No blank line in this case.

Oh, yes, there is a blank line between the comment and the struct. It's
a pitty that someone put much effort into writing a usable description,
which is then not seen. Anyway, should we find all such occurences in
the kernel tree and fix them, or make a workaround for doxygen?

Regards,
Petr

  reply	other threads:[~2006-06-28 16:13 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
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 [this message]
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=1151511215.8127.74.camel@elijah.suse.cz \
    --to=ptesarik@suse.cz \
    --cc=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
all inboxes | Powered by JetHome®