From: Chao Yu <yuchao0@huawei.com>
To: Jia Yang <jiayang5@huawei.com>, <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: Change the type of f2fs_flush_inline_data() to void
Date: Fri, 24 Jul 2020 09:34:04 +0800 [thread overview]
Message-ID: <11953828-cbdb-a5f4-b054-556640516d0a@huawei.com> (raw)
In-Reply-To: <20200721034914.51210-1-jiayang5@huawei.com>
On 2020/7/21 11:49, Jia Yang wrote:
> The return value of f2fs_flush_inline_data() is not used,
> so delete it.
>
> Signed-off-by: Jia Yang <jiayang5@huawei.com>
The patch looks good to me, however f2fs_flush_inline_data() should be
reverted, so let's see...
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Thanks,
> ---
> fs/f2fs/f2fs.h | 2 +-
> fs/f2fs/node.c | 4 +---
> 2 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/fs/f2fs/f2fs.h b/fs/f2fs/f2fs.h
> index b35a50f4953c..cf808aa749bc 100644
> --- a/fs/f2fs/f2fs.h
> +++ b/fs/f2fs/f2fs.h
> @@ -3275,7 +3275,7 @@ void f2fs_ra_node_page(struct f2fs_sb_info *sbi, nid_t nid);
> struct page *f2fs_get_node_page(struct f2fs_sb_info *sbi, pgoff_t nid);
> struct page *f2fs_get_node_page_ra(struct page *parent, int start);
> int f2fs_move_node_page(struct page *node_page, int gc_type);
> -int f2fs_flush_inline_data(struct f2fs_sb_info *sbi);
> +void f2fs_flush_inline_data(struct f2fs_sb_info *sbi);
> int f2fs_fsync_node_pages(struct f2fs_sb_info *sbi, struct inode *inode,
> struct writeback_control *wbc, bool atomic,
> unsigned int *seq_id);
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index 03e24df1c84f..6a95bbcb8313 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -1814,12 +1814,11 @@ static bool flush_dirty_inode(struct page *page)
> return true;
> }
>
> -int f2fs_flush_inline_data(struct f2fs_sb_info *sbi)
> +void f2fs_flush_inline_data(struct f2fs_sb_info *sbi)
> {
> pgoff_t index = 0;
> struct pagevec pvec;
> int nr_pages;
> - int ret = 0;
>
> pagevec_init(&pvec);
>
> @@ -1858,7 +1857,6 @@ int f2fs_flush_inline_data(struct f2fs_sb_info *sbi)
> pagevec_release(&pvec);
> cond_resched();
> }
> - return ret;
> }
>
> int f2fs_sync_node_pages(struct f2fs_sb_info *sbi,
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2020-07-24 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 3:49 [f2fs-dev] [PATCH] f2fs: Change the type of f2fs_flush_inline_data() to void Jia Yang
2020-07-24 1:34 ` Chao Yu [this message]
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=11953828-cbdb-a5f4-b054-556640516d0a@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--cc=jiayang5@huawei.com \
--cc=linux-f2fs-devel@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;
as well as URLs for NNTP newsgroup(s).