public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Kim <jaegeuk.kim@samsung.com>
Cc: f2fs <linux-f2fs-devel@lists.sourceforge.net>,
	fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/7] f2fs: some fix and cleanup about flush_merge
Date: Mon, 14 Apr 2014 09:18:04 +0800	[thread overview]
Message-ID: <534B374C.8030009@cn.fujitsu.com> (raw)
In-Reply-To: <5347BAA5.6070104@cn.fujitsu.com>

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(-)
> 



  reply	other threads:[~2014-04-14  1:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11  9:49 [PATCH 0/7] f2fs: some fix and cleanup about flush_merge Gu Zheng
2014-04-14  1:18 ` Gu Zheng [this message]
2014-04-14  1:44   ` Jaegeuk Kim
2014-04-14  1:48     ` Gu Zheng

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=534B374C.8030009@cn.fujitsu.com \
    --to=guz.fnst@cn.fujitsu.com \
    --cc=jaegeuk.kim@samsung.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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