linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Haicheng Li <haicheng.li@linux.intel.com>
To: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Cc: linux-fsdevel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Haicheng Li <haicheng.lee@gmail.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Huajun Li <huajun.li@intel.com>
Subject: Re: [PATCH] f2fs: fix build warning for f2fs_has_inline_data()
Date: Fri, 27 Dec 2013 18:55:48 +0800	[thread overview]
Message-ID: <20131227105548.GA10857@hli22-desktop> (raw)
In-Reply-To: <1388136123.2101.310.camel@kjgkr>

On Fri, Dec 27, 2013 at 06:22:03PM +0900, Jaegeuk Kim wrote:
> Hi,
> 
> Could you refer the following patch that I sent?
> 
> Re: [PATCH 5/6] f2fs: add the number of inline_data files to status info

yes, your patch should have fixed it. thanks.

      reply	other threads:[~2013-12-27 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-27  6:45 [PATCH] f2fs: fix build warning for f2fs_has_inline_data() Haicheng Li
2013-12-27  9:22 ` Jaegeuk Kim
2013-12-27 10:55   ` Haicheng Li [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=20131227105548.GA10857@hli22-desktop \
    --to=haicheng.li@linux.intel.com \
    --cc=fengguang.wu@intel.com \
    --cc=haicheng.lee@gmail.com \
    --cc=huajun.li@intel.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;
as well as URLs for NNTP newsgroup(s).