From: David Sterba <dsterba@suse.cz>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: check: skip shared node or leaf check for low_memory mode
Date: Tue, 30 Aug 2016 14:08:50 +0200 [thread overview]
Message-ID: <20160830120850.GD16983@suse.cz> (raw)
In-Reply-To: <57C57191.1030909@cn.fujitsu.com>
On Tue, Aug 30, 2016 at 07:44:17PM +0800, Wang Xiaoguang wrote:
> Hi,
>
> On 08/30/2016 07:32 PM, David Sterba wrote:
> > On Tue, Aug 30, 2016 at 09:50:20AM +0800, Qu Wenruo wrote:
> >>> Are they not? The low-memory patchset has been released in 4.7.1, the
> >>> devel branch is always on top of master branch. I see both branches
> >>> pushed to the public git repos so I don't see what you mean.
> >> Unfortunately, the low memory mode is not fully merged into devel branch.
> >>
> >> Only the first part (extent and chunk tree) is merged.
> >>
> >> The second part(fs tree) is not merged yet.
> >>
> >> Patches like the following is not in either devel/master branch:
> >> Lu Fengqi (13):
> >> btrfs-progs: move btrfs_extref_hash() to hash.h
> >> btrfs-progs: check: introduce function to find dir_item
> >> btrfs-progs: check: introduce function to check inode_ref
> >> btrfs-progs: check: introduce function to check inode_extref
> >> btrfs-progs: check: introduce function to find inode_ref
> >> btrfs-progs: check: introduce a function to check dir_item
> >> btrfs-progs: check: introduce function to check file extent
> >> btrfs-progs: check: introduce function to check inode item
> >> btrfs-progs: check: introduce function to check fs root
> >> btrfs-progs: check: introduce function to check root ref
> >> btrfs-progs: check: introduce low_memory mode fs_tree check
> >> btrfs-progs: check: fix the return value bug of cmd_check()
> >> btrfs-progs: check: fix false warning for check_extent_item()
> >>
> >> So Wang found it confusing and unable to apply his patch to devel branch.
> > He could have replied himself, I think the conversation would feel
> > better when we can talk directly :)
> Yes, I agree. I was on leave for a while this morning :)
Doh, I may be confused by the names, I mean that I've never seen a mail
from 'Lu Fengqi'.
prev parent reply other threads:[~2016-08-30 12:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 9:59 [PATCH] btrfs-progs: check: skip shared node or leaf check for low_memory mode Wang Xiaoguang
2016-08-24 12:44 ` David Sterba
2016-08-25 5:30 ` Wang Xiaoguang
2016-08-29 15:20 ` David Sterba
2016-08-30 1:50 ` Qu Wenruo
2016-08-30 11:32 ` David Sterba
2016-08-30 11:44 ` Wang Xiaoguang
2016-08-30 12:08 ` David Sterba [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=20160830120850.GD16983@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
--cc=wangxg.fnst@cn.fujitsu.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 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.