From: Lee Jones <lee.jones@linaro.org>
To: lee.jones@linaro.org
Cc: linux-kernel@vger.kernel.org,
Anton Altaparmakov <anton@tuxera.com>,
linux-ntfs-dev@lists.sourceforge.net
Subject: [PATCH 12/15] fs: ntfs: file: Provide missing descriptions for 'start' and 'end'
Date: Thu, 20 May 2021 13:00:40 +0100 [thread overview]
Message-ID: <20210520120043.3462759-13-lee.jones@linaro.org> (raw)
In-Reply-To: <20210520120043.3462759-1-lee.jones@linaro.org>
Fixes the following W=1 kernel build warning(s):
fs/ntfs/file.c:1969: warning: Function parameter or member 'start' not described in 'ntfs_file_fsync'
fs/ntfs/file.c:1969: warning: Function parameter or member 'end' not described in 'ntfs_file_fsync'
Cc: Anton Altaparmakov <anton@tuxera.com>
Cc: linux-ntfs-dev@lists.sourceforge.net
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
fs/ntfs/file.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/fs/ntfs/file.c b/fs/ntfs/file.c
index e5aab265dff19..1f3d8804324c1 100644
--- a/fs/ntfs/file.c
+++ b/fs/ntfs/file.c
@@ -1943,6 +1943,8 @@ static ssize_t ntfs_file_write_iter(struct kiocb *iocb, struct iov_iter *from)
/**
* ntfs_file_fsync - sync a file to disk
* @filp: file to be synced
+ * @start: offset in bytes where the range starts
+ * @end: offset in bytes where the range ends (inclusive)
* @datasync: if non-zero only flush user data and not metadata
*
* Data integrity sync of a file to disk. Used for fsync, fdatasync, and msync
--
2.31.1
next prev parent reply other threads:[~2021-05-20 12:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 12:00 [PATCH 00/15] Rid W=1 warnings from FS {GFS2,NTFS} Lee Jones
2021-05-20 12:00 ` [PATCH 01/15] fs: gfs2: bmap: Demote half-complete kernel-doc headers fix others Lee Jones
2021-05-20 12:00 ` [PATCH 02/15] fs: gfs2: glock: Fix some deficient kernel-doc headers and demote non-conformant ones Lee Jones
2021-05-21 3:13 ` Andreas Gruenbacher
2021-05-21 6:58 ` Lee Jones
2021-05-21 7:01 ` Lee Jones
2021-05-20 12:00 ` [PATCH 03/15] fs: ntfs: namei: Demote non-conformant kernel-doc headers Lee Jones
2021-05-20 12:00 ` [PATCH 04/15] fs: ntfs: unistr: Add missing param descriptions for 'name{1,2}_len' Lee Jones
2021-05-20 12:00 ` [PATCH 05/15] fs: ntfs: compress: Demote a few non-conformant kernel-doc headers Lee Jones
2021-05-20 12:00 ` [PATCH 06/15] fs: ntfs: dir: Supply missing descriptions for 'start' and 'end' and demote other headers Lee Jones
2021-05-20 12:00 ` [PATCH 07/15] fs: ntfs: runlist: Demote non-conformant kernel-doc headers Lee Jones
2021-05-20 12:00 ` [PATCH 08/15] fs: ntfs: inode: Fix incorrect function name and demote file header Lee Jones
2021-05-20 12:00 ` [PATCH 09/15] fs: ntfs: attrib: File headers are not good candidates for kernel-doc Lee Jones
2021-05-20 12:00 ` [PATCH 10/15] fs: ntfs: aops: Demote kernel-doc abuses Lee Jones
2021-05-20 12:00 ` [PATCH 11/15] fs: ntfs: super: Provide missing description and demote non-conformant headers Lee Jones
2021-05-20 12:00 ` Lee Jones [this message]
2021-05-20 12:00 ` [PATCH 13/15] fs: ntfs: mft: File headers to not make good candidates for kernel-doc Lee Jones
2021-05-20 12:00 ` [PATCH 14/15] fs: ntfs: compress: File headers are not " Lee Jones
2021-05-20 12:00 ` [PATCH 15/15] fs: ntfs: runlist: " Lee Jones
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=20210520120043.3462759-13-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=anton@tuxera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
/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®