From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] kernel-doc: fix function name in usercopy.c
Date: Mon, 9 Oct 2006 15:07:36 +0200 [thread overview]
Message-ID: <200610091507.36988.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <20061008203617.f3ca1270.rdunlap@xenotime.net>
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Randy Dunlap wrote:
> On Mon, 9 Oct 2006 07:28:51 +0400 Alexey Dobriyan wrote:
> > On Sun, Oct 08, 2006 at 07:44:29PM -0700, Randy Dunlap wrote:
> > > /**
> > > - * strlen_user: - Get the size of a string in user space.
> > > + * strnlen_user: - Get the size of a string in user space.
> >
> > It's better to not spend time fixing mismatches, but to teach kernel-doc
> > extract function name from function itself.
> >
> > /**
> > * Get the size of a string in user space.
> > * @foo: bar
> > */
> > size_t strnlen_user()
>
> OK, maybe a good idea. I'll add that to the wish list.
> However, we have seen examples of:
>
> /**
> * doc for foo
> */
> int foo(int arg)
> {
> }
>
> then someone inserts a new function bar() between the kernel-doc
> and foo(). How would we catch that (automated)?
> other than by our review process?
Warn if the function signature of the documented function does not match the
function and throw away the manpage then.
Eike
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-10-09 13:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 2:44 [PATCH] kernel-doc: fix function name in usercopy.c Randy Dunlap
2006-10-09 3:28 ` Alexey Dobriyan
2006-10-09 3:36 ` Randy Dunlap
2006-10-09 13:07 ` Rolf Eike Beer [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=200610091507.36988.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.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