From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Kim <jaegeuk.kim@samsung.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
f2fs <linux-f2fs-devel@lists.sourceforge.net>
Subject: [PATCH 0/5] f2fs: some minor fix and clean up
Date: Fri, 07 Mar 2014 18:43:16 +0800 [thread overview]
Message-ID: <5319A2C4.7040404@cn.fujitsu.com> (raw)
Gu Zheng (5):
f2fs: update start nid once each circle
f2fs: remove the unused ctor argument of f2fs_kmem_cache_create()
f2fs: format segment_info's show for better legibility
f2fs: optimize restore_node_summary slightly
f2fs: add a wait queue to avoid unnecessary build_free_nid
fs/f2fs/checkpoint.c | 4 +-
fs/f2fs/f2fs.h | 5 ++-
fs/f2fs/gc.c | 2 +-
fs/f2fs/node.c | 64 ++++++++++++++++++++++++++++----------------------
fs/f2fs/recovery.c | 2 +-
fs/f2fs/segment.c | 9 ++++--
fs/f2fs/super.c | 9 ++++---
7 files changed, 54 insertions(+), 41 deletions(-)
--
1.7.7
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
WARNING: multiple messages have this Message-ID (diff)
From: Gu Zheng <guz.fnst@cn.fujitsu.com>
To: Kim <jaegeuk.kim@samsung.com>
Cc: f2fs <linux-f2fs-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/5] f2fs: some minor fix and clean up
Date: Fri, 07 Mar 2014 18:43:16 +0800 [thread overview]
Message-ID: <5319A2C4.7040404@cn.fujitsu.com> (raw)
Gu Zheng (5):
f2fs: update start nid once each circle
f2fs: remove the unused ctor argument of f2fs_kmem_cache_create()
f2fs: format segment_info's show for better legibility
f2fs: optimize restore_node_summary slightly
f2fs: add a wait queue to avoid unnecessary build_free_nid
fs/f2fs/checkpoint.c | 4 +-
fs/f2fs/f2fs.h | 5 ++-
fs/f2fs/gc.c | 2 +-
fs/f2fs/node.c | 64 ++++++++++++++++++++++++++++----------------------
fs/f2fs/recovery.c | 2 +-
fs/f2fs/segment.c | 9 ++++--
fs/f2fs/super.c | 9 ++++---
7 files changed, 54 insertions(+), 41 deletions(-)
--
1.7.7
next reply other threads:[~2014-03-07 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 10:43 Gu Zheng [this message]
2014-03-07 10:43 ` [PATCH 0/5] f2fs: some minor fix and clean up 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=5319A2C4.7040404@cn.fujitsu.com \
--to=guz.fnst@cn.fujitsu.com \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.