From: JeffleXu <jefflexu@linux.alibaba.com>
To: Khalid Masum <khalid.masum.92@gmail.com>,
linux-cachefs@redhat.com, linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [Linux-cachefs] [PATCH v2] fscache: fix misdocumented parameter
Date: Thu, 18 Aug 2022 17:32:09 +0800 [thread overview]
Message-ID: <16a13735-1349-9927-0f7b-1c5622198e2a@linux.alibaba.com> (raw)
In-Reply-To: <20220818040738.12036-1-khalid.masum.92@gmail.com>
On 8/18/22 12:07 PM, Khalid Masum wrote:
> This patch fixes two warnings generated by make docs. The functions
> fscache_use_cookie and fscache_unuse_cookie, both have a parameter
> named cookie. But they are documented with the name "object" with
> unclear description. Which generates the warning when creating docs.
>
> This commit will replace the currently misdocumented parameter names
> with the correct ones while adding proper descriptions.
>
> CC: Randy Dunlap <rdunlap@infradead.org>
> Signed-off-by: Khalid Masum <khalid.masum.92@gmail.com>
LGTM.
Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
> ---
> Changes since v1:
> - Update commit message.
> - Link: https://lore.kernel.org/lkml/20220521142446.4746-1-khalid.masum.92@gmail.com/
>
> include/linux/fscache.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/fscache.h b/include/linux/fscache.h
> index 720874e6ee94..36e5dd84cf59 100644
> --- a/include/linux/fscache.h
> +++ b/include/linux/fscache.h
> @@ -258,7 +258,7 @@ struct fscache_cookie *fscache_acquire_cookie(struct fscache_volume *volume,
>
> /**
> * fscache_use_cookie - Request usage of cookie attached to an object
> - * @object: Object description
> + * @cookie: The cookie representing the cache object
> * @will_modify: If cache is expected to be modified locally
> *
> * Request usage of the cookie attached to an object. The caller should tell
> @@ -274,7 +274,7 @@ static inline void fscache_use_cookie(struct fscache_cookie *cookie,
>
> /**
> * fscache_unuse_cookie - Cease usage of cookie attached to an object
> - * @object: Object description
> + * @cookie: The cookie representing the cache object
> * @aux_data: Updated auxiliary data (or NULL)
> * @object_size: Revised size of the object (or NULL)
> *
--
Thanks,
Jingbo
prev parent reply other threads:[~2022-08-18 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 4:07 Khalid Masum
2022-08-18 9:32 ` JeffleXu [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=16a13735-1349-9927-0f7b-1c5622198e2a@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=khalid.masum.92@gmail.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@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
all inboxes | Powered by JetHome®