From: Xiaofei Tan <tanxiaofei@huawei.com>
To: <viro@zeniv.linux.org.uk>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <linuxarm@huawei.com>, Xiaofei Tan <tanxiaofei@huawei.com>
Subject: [PATCH] fs: fix ioctl.c kernel-doc warnings
Date: Tue, 15 Sep 2020 21:30:35 +0800 [thread overview]
Message-ID: <1600176635-3717-1-git-send-email-tanxiaofei@huawei.com> (raw)
Fix following warnings:
fs/ioctl.c:109: warning: Excess function parameter 'fieinfo' description in 'SET_UNKNOWN_FLAGS'
fs/ioctl.c:109: warning: Excess function parameter 'logical' description in 'SET_UNKNOWN_FLAGS'
fs/ioctl.c:109: warning: Excess function parameter 'phys' description in 'SET_UNKNOWN_FLAGS'
fs/ioctl.c:109: warning: Excess function parameter 'len' description in 'SET_UNKNOWN_FLAGS'
fs/ioctl.c:109: warning: Excess function parameter 'flags' description in 'SET_UNKNOWN_FLAGS'
Signed-off-by: Xiaofei Tan <tanxiaofei@huawei.com>
---
fs/ioctl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fs/ioctl.c b/fs/ioctl.c
index 4e6cc0a..81b028f 100644
--- a/fs/ioctl.c
+++ b/fs/ioctl.c
@@ -91,6 +91,9 @@ static int ioctl_fibmap(struct file *filp, int __user *p)
return error;
}
+#define SET_UNKNOWN_FLAGS (FIEMAP_EXTENT_DELALLOC)
+#define SET_NO_UNMOUNTED_IO_FLAGS (FIEMAP_EXTENT_DATA_ENCRYPTED)
+#define SET_NOT_ALIGNED_FLAGS (FIEMAP_EXTENT_DATA_TAIL|FIEMAP_EXTENT_DATA_INLINE)
/**
* fiemap_fill_next_extent - Fiemap helper function
* @fieinfo: Fiemap context passed into ->fiemap
@@ -106,9 +109,6 @@ static int ioctl_fibmap(struct file *filp, int __user *p)
* Returns 0 on success, -errno on error, 1 if this was the last
* extent that will fit in user array.
*/
-#define SET_UNKNOWN_FLAGS (FIEMAP_EXTENT_DELALLOC)
-#define SET_NO_UNMOUNTED_IO_FLAGS (FIEMAP_EXTENT_DATA_ENCRYPTED)
-#define SET_NOT_ALIGNED_FLAGS (FIEMAP_EXTENT_DATA_TAIL|FIEMAP_EXTENT_DATA_INLINE)
int fiemap_fill_next_extent(struct fiemap_extent_info *fieinfo, u64 logical,
u64 phys, u64 len, u32 flags)
{
--
2.8.1
reply other threads:[~2020-09-15 14:03 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=1600176635-3717-1-git-send-email-tanxiaofei@huawei.com \
--to=tanxiaofei@huawei.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=viro@zeniv.linux.org.uk \
/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).