From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
stern@rowland.harvard.edu, akpm@linux-foundation.org,
apw@canonical.com, mingo@elte.hu, linux-kernel@vger.kernel.org,
peterz@infradead.org
Subject: Re: [PATCH] Add kerneldoc for flush_scheduled_work()
Date: Thu, 13 Aug 2009 10:04:13 -0500 [thread overview]
Message-ID: <1250175853.3901.34.camel@mulgrave.site> (raw)
In-Reply-To: <20090813145106.GA25333@cmpxchg.org>
On Thu, 2009-08-13 at 16:51 +0200, Johannes Weiner wrote:
> Okay, I came up with a syntax to allow continued lines in short
> descriptions and parameter descriptons.
>
> I can successfully parse
>
> ---
> /**
> * get_tty_driver - find device of a tty
> * ...and everything
I'm not so keen on the ... syntax ... suggestions below
> * @device: device identifier
> * ... to identify the device with
> * ... that is to be matched
> * @index: returns the index of the tty
> * ... for your personal pleasure
> *
> * This routine returns a tty driver structure, given a device number
> * and also passes back the index number.
> *
> * Locking: caller must hold tty_mutex
> */
> ---
>
> to
>
> ---
> Name:
>
> get_tty_driver - find device of a tty and everything
>
> Synopsis:
>
> struct tty_driver * get_tty_driver (dev_t device,
> int * index);
>
> Arguments:
>
> device
> device identifier to identify the device with that is to be matched
> index
> returns the index of the tty for your personal pleasure
>
> Description:
>
> This routine returns a tty driver structure, given a device number
> and also passes back the index number.
> Locking:
>
> caller must hold tty_mutex
> ---
>
> Unfortunately, perl requires me to ignore my pathetic rest of taste,
> so it may well be horribly ugly without me noticing ;) Would the
> following work for you? I will happily incorporate improvements.
>
> Hannes
>
> ---
>
> diff --git a/scripts/kernel-doc b/scripts/kernel-doc
> index b52d340..e427b0a 100755
> --- a/scripts/kernel-doc
> +++ b/scripts/kernel-doc
> @@ -279,6 +279,7 @@ my $doc_special = "\@\%\$\&";
> my $doc_start = '^/\*\*\s*$'; # Allow whitespace at end of comment start.
> my $doc_end = '\*/';
> my $doc_com = '\s*\*\s*';
> +my $doc_cont = $doc_com . '\.\.\.\s*(.+)';
how about making this
$doc_cont = $doc_com.'\s*([^@].*)';
That way anything that doesn't begin with a variable declaration would
be treated as comment continuation. Might need a \s is the brackets to
ensure blank lines are OK and not treated as continuations.
James
next prev parent reply other threads:[~2009-08-13 15:04 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 12:06 [PATCH] Add kerneldoc for flush_scheduled_work() Randy Dunlap
2009-08-13 14:51 ` Johannes Weiner
2009-08-13 15:04 ` James Bottomley [this message]
2009-08-13 16:20 ` Randy Dunlap
2009-08-13 18:08 ` Johannes Weiner
2009-08-14 18:23 ` Randy Dunlap
2009-08-16 19:13 ` [PATCH] scsi: fix func names in kernel-doc Randy Dunlap
2009-08-18 9:04 ` [PATCH] Add kerneldoc for flush_scheduled_work() Johannes Weiner
2009-08-19 22:23 ` Johannes Weiner
2009-08-19 23:21 ` Randy Dunlap
2009-08-19 23:27 ` Randy Dunlap
2009-08-24 19:06 ` Johannes Weiner
2009-08-24 19:27 ` Randy Dunlap
2009-08-24 20:09 ` Johannes Weiner
2009-08-24 20:25 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2009-08-12 18:14 Randy Dunlap
2009-08-11 21:06 Alan Stern
2009-08-12 9:41 ` Ingo Molnar
2009-08-12 10:47 ` Peter Zijlstra
2009-08-12 10:51 ` Ingo Molnar
2009-08-12 14:13 ` Alan Stern
2009-08-12 14:17 ` Ingo Molnar
2009-08-12 16:22 ` James Bottomley
2009-08-13 7:25 ` Ingo Molnar
2009-08-13 8:47 ` Johannes Weiner
2009-08-13 10:03 ` Ingo Molnar
2009-08-13 14:37 ` James Bottomley
2009-08-12 14:01 ` James Bottomley
2009-08-12 14:54 ` Alan Stern
2009-08-12 15:00 ` James Bottomley
2009-08-12 15:44 ` Alan Stern
2009-08-12 15:58 ` James Bottomley
2009-08-12 16:23 ` Alan Stern
2009-08-12 17:02 ` James Bottomley
2009-08-12 17:25 ` Alan Stern
2009-08-12 17:36 ` James Bottomley
2009-08-12 18:16 ` Alan Stern
2009-08-12 18:27 ` James Bottomley
2009-08-12 18:48 ` Alan Stern
2009-08-12 20:28 ` James Bottomley
2009-08-12 20:41 ` Alan Stern
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=1250175853.3901.34.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=randy.dunlap@oracle.com \
--cc=stern@rowland.harvard.edu \
/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