From: Baokun Li <libaokun1@huawei.com>
To: <viro@zeniv.linux.org.uk>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <weiyongjun1@huawei.com>, <yuehaibing@huawei.com>,
<yangjihong1@huawei.com>, <yukuai3@huawei.com>,
<libaokun1@huawei.com>
Subject: [PATCH -next] fs/file: fix doc warnings in file.c
Date: Tue, 8 Jun 2021 10:44:22 +0800 [thread overview]
Message-ID: <20210608024422.2752247-1-libaokun1@huawei.com> (raw)
Fixes the following W=1 kernel build warning(s):
fs/file.c:655: warning: Function parameter or
member 'fdt' not described in 'last_fd'
fs/file.c:655: warning: Excess function
parameter 'cur_fds' description in 'last_fd'
fs/file.c:703: warning: Function parameter or
member 'flags' not described in '__close_range'
Signed-off-by: Baokun Li <libaokun1@huawei.com>
---
fs/file.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/file.c b/fs/file.c
index d8afa8266859..c6d99c875dea 100644
--- a/fs/file.c
+++ b/fs/file.c
@@ -645,7 +645,7 @@ EXPORT_SYMBOL(close_fd); /* for ksys_close() */
/**
* last_fd - return last valid index into fd table
- * @cur_fds: files struct
+ * @fdt: fdtable struct
*
* Context: Either rcu read lock or files_lock must be held.
*
@@ -695,7 +695,7 @@ static inline void __range_close(struct files_struct *cur_fds, unsigned int fd,
*
* @fd: starting file descriptor to close
* @max_fd: last file descriptor to close
- *
+ * @flags: flags of starting file
* This closes a range of file descriptors. All file descriptors
* from @fd up to and including @max_fd are closed.
*/
--
2.31.1
reply other threads:[~2021-06-08 2:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210608024422.2752247-1-libaokun1@huawei.com \
--to=libaokun1@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=weiyongjun1@huawei.com \
--cc=yangjihong1@huawei.com \
--cc=yuehaibing@huawei.com \
--cc=yukuai3@huawei.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).