From: Tejun Heo <tj@kernel.org>
To: Naohiro Aota <naota@elisp.net>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Jiri Kosina <jkosina@suse.cz>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH 1/2] idr: fix kernel-doc warnings.
Date: Mon, 30 Aug 2010 17:53:05 +0200 [thread overview]
Message-ID: <4C7BD3E1.2000806@kernel.org> (raw)
In-Reply-To: <m27hj8cdsw.fsf@elisp.net>
On 08/30/2010 05:37 PM, Naohiro Aota wrote:
> Fix the following kernel-doc warnings.
>
> % perl scripts/kernel-doc lib/idr.c > /dev/null
> Warning(lib/idr.c:300): No description found for parameter 'starting_id'
> Warning(lib/idr.c:300): Excess function parameter 'start_id' description in 'idr_get_new_above'
> Warning(lib/idr.c:485): No description found for parameter 'idp'
> Warning(lib/idr.c:596): No description found for parameter 'nextidp'
> Warning(lib/idr.c:596): Excess function parameter 'id' description in 'idr_get_next'
> Warning(lib/idr.c:774): No description found for parameter 'starting_id'
> Warning(lib/idr.c:774): Excess function parameter 'staring_id' description in 'ida_get_new_above'
> Warning(lib/idr.c:918): No description found for parameter 'ida'
>
> Signed-off-by: Naohiro Aota <naota@elisp.net>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
next prev parent reply other threads:[~2010-08-30 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 15:37 [PATCH 1/2] idr: fix kernel-doc warnings Naohiro Aota
2010-08-30 15:39 ` [PATCH 2/2] idr: describe how nextidp works in idr_get_next() Naohiro Aota
2010-08-30 15:55 ` Tejun Heo
2010-08-31 4:02 ` Naohiro Aota
2010-08-31 7:41 ` Tejun Heo
2010-08-31 7:44 ` Jiri Kosina
2010-08-30 15:53 ` Tejun Heo [this message]
2010-08-31 7:32 ` [PATCH 1/2] idr: fix kernel-doc warnings Jiri Kosina
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=4C7BD3E1.2000806@kernel.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naota@elisp.net \
--cc=paulmck@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).