From: Randy Dunlap <rdunlap@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Philipp Reisner <philipp.reisner@linbit.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
drbd-dev@tron.linbit.com, Jiri Pirko <jiri@nvidia.com>,
netdev@vger.kernel.org, Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH] lib: remove "expecting prototype" kernel-doc warnings
Date: Tue, 13 Apr 2021 11:31:25 -0700 [thread overview]
Message-ID: <02166180-2ffe-ed4b-91dc-cde198004fcc@infradead.org> (raw)
In-Reply-To: <20210413111828.365dcbcb2e24bfaa91e855ff@linux-foundation.org>
On 4/13/21 11:18 AM, Andrew Morton wrote:
> On Sun, 11 Apr 2021 15:17:56 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
>> Fix various kernel-doc warnings in lib/ due to missing or
>> erroneous function names.
>> Add kernel-doc for some function parameters that was missing.
>> Use kernel-doc "Return:" notation in earlycpio.c.
>>
>> Quietens the following warnings:
>>
>> ../lib/earlycpio.c:61: warning: expecting prototype for cpio_data find_cpio_data(). Prototype was for find_cpio_data() instead
>>
>> ../lib/lru_cache.c:640: warning: expecting prototype for lc_dump(). Prototype was for lc_seq_dump_details() instead
>> lru_cache.c:90: warning: Function parameter or member 'cache' not described in 'lc_create'
>
> I'm still seeing this.
>
Weird. I can't reproduce it.
>> lru_cache.c:90: warning: Function parameter or member 'cache' not described in 'lc_create'
>
> But it looks OK:
>
Yes.
> /**
> * lc_create - prepares to track objects in an active set
> * @name: descriptive name only used in lc_seq_printf_stats and lc_seq_dump_details
> * @cache: cache root pointer
> * @max_pending_changes: maximum changes to accumulate until a transaction is required
> * @e_count: number of elements allowed to be active simultaneously
> * @e_size: size of the tracked objects
> * @e_off: offset to the &struct lc_element member in a tracked object
> *
> * Returns a pointer to a newly initialized struct lru_cache on success,
> * or NULL on (allocation) failure.
> */
> struct lru_cache *lc_create(const char *name, struct kmem_cache *cache,
> unsigned max_pending_changes,
> unsigned e_count, size_t e_size, size_t e_off)
> {
>
I'll keep looking...
--
~Randy
prev parent reply other threads:[~2021-04-13 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-11 22:17 [PATCH] lib: remove "expecting prototype" kernel-doc warnings Randy Dunlap
2021-04-13 18:18 ` Andrew Morton
2021-04-13 18:31 ` Randy Dunlap [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=02166180-2ffe-ed4b-91dc-cde198004fcc@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=drbd-dev@tron.linbit.com \
--cc=jiri@nvidia.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=philipp.reisner@linbit.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).