From: Randy Dunlap <rdunlap@infradead.org>
To: Yang Li <yang.lee@linux.alibaba.com>,
viro@zeniv.linux.org.uk, brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] fs: Fix one kernel-doc comment
Date: Thu, 10 Aug 2023 22:03:37 -0700 [thread overview]
Message-ID: <a238c84e-3ddb-ef0b-66e4-b90d142fcd48@infradead.org> (raw)
In-Reply-To: <20230811014359.4960-1-yang.lee@linux.alibaba.com>
On 8/10/23 18:43, Yang Li wrote:
> Fix one kernel-doc comment to silence the warning:
>
> fs/read_write.c:88: warning: Function parameter or member 'maxsize' not described in 'generic_file_llseek_size'
>
> Signed-off-by: Yang Li <yang.lee@linux.alibaba.com>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Thanks.
> ---
> fs/read_write.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/read_write.c b/fs/read_write.c
> index b07de77ef126..4771701c896b 100644
> --- a/fs/read_write.c
> +++ b/fs/read_write.c
> @@ -71,7 +71,7 @@ EXPORT_SYMBOL(vfs_setpos);
> * @file: file structure to seek on
> * @offset: file offset to seek to
> * @whence: type of seek
> - * @size: max size of this file in file system
> + * @maxsize: max size of this file in file system
> * @eof: offset used for SEEK_END position
> *
> * This is a variant of generic_file_llseek that allows passing in a custom
--
~Randy
next prev parent reply other threads:[~2023-08-11 5:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 1:43 [PATCH -next] fs: Fix one kernel-doc comment Yang Li
2023-08-11 5:03 ` Randy Dunlap [this message]
2023-08-11 6:58 ` Christian Brauner
-- strict thread matches above, loose matches on Subject: below --
2022-05-26 13:37 Yang Li
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=a238c84e-3ddb-ef0b-66e4-b90d142fcd48@infradead.org \
--to=rdunlap@infradead.org \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yang.lee@linux.alibaba.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).