mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Khalid Masum <khalid.masum.92@gmail.com>,
	linux-kernel-mentees@lists.linuxfoundation.org
Cc: Shuah Khan <skhan@linuxfoundation.org>,
	David Howells <dhowells@redhat.com>,
	linux-cachefs@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fscache: fix misdocumented parameter name
Date: Sat, 21 May 2022 08:31:54 -0700	[thread overview]
Message-ID: <c02b4ae7-218e-2349-afcb-9ada25beb934@infradead.org> (raw)
In-Reply-To: <20220521142446.4746-1-khalid.masum.92@gmail.com>



On 5/21/22 07:24, Khalid Masum wrote:
> To fix warning generated by make docs in the file fscache.h:
> The functions fscache_use_cookie and fscache_unuse_cookie have a
> parameter named cookie. But they are documented with the name "object".
> Which generates warning when creating docs. This commit will replace
> the documentation with a better one named "cookie". This new
> documentation
> line is taken from the function fscache_update_cookie in the same
> file.
> 
> Signed-off-by: Khalid Masum <khalid.masum.92@gmail.com>

LGTM. Thanks.

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

> ---
>  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 e25539072..32cf593b8 100644
> --- a/include/linux/fscache.h
> +++ b/include/linux/fscache.h
> @@ -256,7 +256,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
> @@ -272,7 +272,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)
>   *

-- 
~Randy

      reply	other threads:[~2022-05-21 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 14:24 Khalid Masum
2022-05-21 15: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=c02b4ae7-218e-2349-afcb-9ada25beb934@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=dhowells@redhat.com \
    --cc=khalid.masum.92@gmail.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.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®