linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao2.yu@samsung.com>
To: 'Jaegeuk Kim' <jaegeuk@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: RE: [f2fs-dev] [PATCH v2] f2fs: do not write any node pages related to orphan inodes
Date: Thu, 20 Aug 2015 17:03:59 +0800	[thread overview]
Message-ID: <01b601d0db27$4123d820$c36b8860$@samsung.com> (raw)
In-Reply-To: <20150812171041.GA27478@jaegeuk-mac02.mot.com>

Reviewed-by: Chao Yu <chao2.yu@samsung.com>

      reply	other threads:[~2015-08-20  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11 22:02 [PATCH] f2fs: do not write any node pages related to orphan inodes Jaegeuk Kim
2015-08-12  9:45 ` [f2fs-dev] " Chao Yu
2015-08-12 17:10   ` [f2fs-dev] [PATCH v2] " Jaegeuk Kim
2015-08-20  9:03     ` 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='01b601d0db27$4123d820$c36b8860$@samsung.com' \
    --to=chao2.yu@samsung.com \
    --cc=jaegeuk@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).