From: Randy Dunlap <rdunlap@xenotime.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernel-doc problem
Date: Thu, 19 Aug 2010 08:30:28 -0700 [thread overview]
Message-ID: <20100819083028.6509ab3e.rdunlap@xenotime.net> (raw)
In-Reply-To: <1282224019.4507.3.camel@jlt3.sipsolutions.net>
On Thu, 19 Aug 2010 15:20:19 +0200 Johannes Berg wrote:
> Randy, all,
>
> I'm running into a problem where something that I want to be part of a
> description of a struct member or function parameter gets parsed as a
> new section. You can easily see the problem by running below test file
> through kernel-doc, clearly the intent is not to have a new section in
> the middle of function argument descriptions, but I have no idea how I
> could fix this.
>
> I'd appreciate if you could take a look.
>
> Thanks,
> Johannes
>
> --- here's the file ---
> /**
> * fn - test
> *
> * @a: This is just a non-sense and totally useless dummy function
> * argument: it has absolutely no effect.
> */
> void fn(int a)
> {
> }
Colons (':') are bad. They cause a section instance.
I don't know how to fix it (inside kernel-doc or docproc or xmlto or wherever).
Sometimes I change colon to "--" or "." or something that makes some sense,
but colon is still the better choice if it would work.
The word "example" has a similar problem. It causes an <informalexample>
markup to begin, but it's not always terminated properly.
See recent commit 3d2be54bab7efd97b642838b9c883869ca5b98be.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-08-19 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 13:20 Johannes Berg
2010-08-19 15:30 ` Randy Dunlap [this message]
2010-08-19 15:37 ` Johannes Berg
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=20100819083028.6509ab3e.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=johannes@sipsolutions.net \
--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®