[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <1397439855.24638.24.camel@kjgkr>
Date: Mon, 14 Apr 2014 10:44:15 +0900
From: Jaegeuk Kim <jaegeuk.kim@...sung.com>
To: Gu Zheng <guz.fnst@...fujitsu.com>
Cc: f2fs <linux-f2fs-devel@...ts.sourceforge.net>,
fsdevel <linux-fsdevel@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/7] f2fs: some fix and cleanup about flush_merge
Hi Gu,
I just started to review the patches and merge them individually though.
Since I've been internally doing in my local tree, so that should be no
problem. I'll roll back to the latest point.
Anyway, thank you for your work. :)
2014-04-14 (월), 09:18 +0800, Gu Zheng:
> Hi All,
> There seems to be a mistake in "[PATCH 2/7]f2fs: remove the unuseful "issue_tail" list",
> and the whole patchset needs to be reworked. So please ignore this one.
> Sorry for the noise.
>
> Regards,
> Gu
> On 04/11/2014 05:49 PM, Gu Zheng wrote:
>
> > Gu Zheng (7):
> > f2fs: put the bio when issue_flush completed
> > f2fs: remove the unuseful "issue_tail" list
> > f2fs: use __GFP_ZERO to avoid appending set-NULL
> > f2fs: enable flush_merge only in f2fs is not read-only
> > f2fs: add the flush_merge handle in the remount flow
> > f2fs: introduce struct flush_cmd_control to wrap the flush_merge
> > fields
> > f2fs: introduce help function {create,destroy}_flush_cmd_control
> >
> > fs/f2fs/f2fs.h | 17 ++++++---
> > fs/f2fs/segment.c | 102 +++++++++++++++++++++++++++++++++++-----------------
> > fs/f2fs/super.c | 32 ++++++++++++++--
> > 3 files changed, 107 insertions(+), 44 deletions(-)
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Jaegeuk Kim
Samsung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists