From: Souptick Joarder <jrdr.linux@gmail.com>
To: akpm@linux-foundation.org
Cc: viro@zeniv.linux.org.uk, darrick.wong@oracle.com,
agruenba@redhat.com, jack@suse.cz, dchinner@redhat.com,
tytso@mit.edu, rpeterso@redhat.com, gregkh@linuxfoundation.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
willy@infradead.org
Subject: [PATCH] fs: iomap: Change return type to vm_fault_t
Date: Mon, 2 Jul 2018 21:13:54 +0530 [thread overview]
Message-ID: <20180702154354.GA3919@jordon-HP-15-Notebook-PC> (raw)
Return type has been changed to vm_fault_t type for
iomap_page_mkwrite().
see commit 1c8f422059ae ("mm: change return type to
vm_fault_t") for reference.
Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
Reviewed-by: Matthew Wilcox <mawilcox@microsoft.com>
---
fs/iomap.c | 2 +-
include/linux/iomap.h | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/fs/iomap.c b/fs/iomap.c
index afd1635..58477ee 100644
--- a/fs/iomap.c
+++ b/fs/iomap.c
@@ -443,7 +443,7 @@ static int iomap_dax_zero(loff_t pos, unsigned offset, unsigned bytes,
return length;
}
-int iomap_page_mkwrite(struct vm_fault *vmf, const struct iomap_ops *ops)
+vm_fault_t iomap_page_mkwrite(struct vm_fault *vmf, const struct iomap_ops *ops)
{
struct page *page = vmf->page;
struct inode *inode = file_inode(vmf->vma->vm_file);
diff --git a/include/linux/iomap.h b/include/linux/iomap.h
index 19a07de..666b717 100644
--- a/include/linux/iomap.h
+++ b/include/linux/iomap.h
@@ -3,6 +3,7 @@
#define LINUX_IOMAP_H 1
#include <linux/types.h>
+#include <linux/mm_types.h>
struct fiemap_extent_info;
struct inode;
@@ -88,7 +89,8 @@ int iomap_zero_range(struct inode *inode, loff_t pos, loff_t len,
bool *did_zero, const struct iomap_ops *ops);
int iomap_truncate_page(struct inode *inode, loff_t pos, bool *did_zero,
const struct iomap_ops *ops);
-int iomap_page_mkwrite(struct vm_fault *vmf, const struct iomap_ops *ops);
+vm_fault_t iomap_page_mkwrite(struct vm_fault *vmf,
+ const struct iomap_ops *ops);
int iomap_fiemap(struct inode *inode, struct fiemap_extent_info *fieinfo,
loff_t start, loff_t len, const struct iomap_ops *ops);
loff_t iomap_seek_hole(struct inode *inode, loff_t offset,
--
1.9.1
next reply other threads:[~2018-07-02 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 15:43 Souptick Joarder [this message]
2018-07-02 17:52 ` [PATCH] fs: iomap: Change return type to vm_fault_t Andreas Gruenbacher
2018-07-03 21:39 ` Darrick J. Wong
2018-07-03 21:52 ` Andreas Gruenbacher
2018-07-20 5:01 ` Souptick Joarder
2018-07-20 6:09 ` Darrick J. Wong
2018-07-20 6:55 ` Souptick Joarder
2018-07-20 19:36 ` Matthew Wilcox
-- strict thread matches above, loose matches on Subject: below --
2018-08-27 17:20 Souptick Joarder
2018-04-14 20:02 Souptick Joarder
2018-05-14 18:15 ` Souptick Joarder
2018-05-15 7:10 ` Christoph Hellwig
2018-05-15 8:00 ` Souptick Joarder
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=20180702154354.GA3919@jordon-HP-15-Notebook-PC \
--to=jrdr.linux@gmail.com \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpeterso@redhat.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).