All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: "Xu, Wen" <wen.xu@gatech.edu>
Cc: "linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: Questions about commit f2fs: fix to avoid broken of dnode block list
Date: Wed, 4 Jul 2018 14:58:08 +0800	[thread overview]
Message-ID: <e71300ba-b88e-dc35-b141-6e2cb3464713@huawei.com> (raw)
In-Reply-To: <808556C6-7CCE-4D50-9F54-F34072A83AE3@gatech.edu>

Hi Wen,

On 2018/7/4 12:34, Xu, Wen wrote:
> Hi Chao,
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git/commit/?h=f2fs-dev&id=0ac2890156ab517a8ac79849ee5abab7ad60310b
> 
> In this patch: f2fs: fix to avoid broken of dnode block list
> -int f2fs_wait_on_node_pages_writeback(struct f2fs_sb_info *sbi, nid_t ino)
> +int f2fs_wait_on_node_pages_writeback(struct f2fs_sb_info *sbi)
> 
> You modify f2fs_wait_on_node_pages_writeback() in file.c but seems not modifying the declaration in f2fs.h? Which makes compilation failed…

Sorry, my mistake, it added definition change located in f2fs.h into incorrect
patch when I split one patch to below two:

f2fs: let checkpoint flush dnode page of regular
f2fs: fix to avoid broken of dnode block list

I will update them, thanks for your report. :)

Thanks,

> 
> Thanks,
> -Wen
> 


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

      reply	other threads:[~2018-07-04  6:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-04  4:34 Questions about commit f2fs: fix to avoid broken of dnode block list Xu, Wen
2018-07-04  6:58 ` 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=e71300ba-b88e-dc35-b141-6e2cb3464713@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=wen.xu@gatech.edu \
    /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.