linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, Chao Yu <yuchao0@huawei.com>
Subject: Re: [PATCH] f2fs: support plain user/group quota
Date: Sun, 9 Jul 2017 00:15:47 +0800	[thread overview]
Message-ID: <3cb2d6d3-7ece-9d95-e95e-44dd93f431c7@kernel.org> (raw)
In-Reply-To: <20170707191233.GA29629@jaegeuk-macbookpro.roam.corp.google.com>

Hi Jaegeuk,

On 2017/7/8 3:12, Jaegeuk Kim wrote:
> Hi Chao,
> 
> I've updated your patch like this.
> 
> - modify description 
> - use filemap_write_and_wait() directly aligned to the below v2 patch.
> 
>   f2fs: avoid deadlock caused by lock order of page and

Looks good to me.

I've updated doc in the patch rebased on this version as well.

Thanks,

      reply	other threads:[~2017-07-08 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-06 13:52 [PATCH] f2fs: support plain user/group quota Chao Yu
2017-07-07 19:12 ` Jaegeuk Kim
2017-07-08 16:15   ` 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=3cb2d6d3-7ece-9d95-e95e-44dd93f431c7@kernel.org \
    --to=chao@kernel.org \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.com \
    /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).