From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, mingo@elte.hu
Subject: Re: [PATCH] ktime/hrtimer: fix kernel-doc comments
Date: Mon, 19 Jun 2006 14:20:50 -0700 [thread overview]
Message-ID: <20060619142050.c4765cef.rdunlap@xenotime.net> (raw)
In-Reply-To: <1150751733.6780.3.camel@localhost.localdomain>
On Mon, 19 Jun 2006 23:15:33 +0200 Thomas Gleixner wrote:
> On Mon, 2006-06-19 at 14:11 -0700, Randy.Dunlap wrote:
> > > My personal preference is to keep that line, as it makes it easier to
> > > read. But as always: de gustibus non est disputandum :)
> >
> > Feel free to send patches for scripts/kernel-doc instead. :)
>
> Yeah, Russell King pointed me to the nano-howto 2 minutes ago. Not
> reading docs is always backfiring at some point. :(
>
> Seriously, is it hard to fix ? I'm not good with perl, so its likely
> that I would make more mess than fixups.
I don't know for sure. I have looked at it a bit and
it's messy code IMHO. Might be easier/better just to rewrite
the function (comment) header parsing.
Andrew also wants the short function description to be able to be
more than one line. That could/should be incorporated at the same time.
OTOH, it's a defined doc. language and these files contain errors...
---
~Randy
PS: finally fixed Ingo's email address.
next prev parent reply other threads:[~2006-06-19 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 20:09 [PATCH] ktime/hrtimer: fix kernel-doc comments Randy.Dunlap
2006-06-19 21:00 ` Thomas Gleixner
2006-06-19 21:11 ` Randy.Dunlap
2006-06-19 21:15 ` Thomas Gleixner
2006-06-19 21:20 ` Randy.Dunlap [this message]
2006-06-19 21:30 ` Thomas Gleixner
2006-06-19 21:41 ` Randy.Dunlap
2006-06-19 21:45 ` Thomas Gleixner
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=20060619142050.c4765cef.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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