linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Qu Wenruo <quwenruo@cn.fujitsu.com>,
	Zhao Lei <zhaolei@cn.fujitsu.com>,
	"'Sean Fu'" <fxinrong@gmail.com>,
	clm@fb.com, anand.jain@oracle.com,
	Filipe Manana <FdManana@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree.
Date: Tue, 6 Sep 2016 11:58:58 +0200	[thread overview]
Message-ID: <20160906095858.GA16983@suse.cz> (raw)
In-Reply-To: <57CE3464.7090107@suse.com>

On Mon, Sep 05, 2016 at 11:13:40PM -0400, Jeff Mahoney wrote:
> >> Since root is only used to get fs_info->chunk_root, why not use fs_info
> >> directly?
> > 
> > Weird.  Exactly this was a part of my fs_info patchset.  I guess I need
> > to go back and check what else is missing.
> 
> Actually, most of this didn't land.  Pretty much anything that's a root
> ->fs_info conversion is in there.

Only half of the patchset has been merged so far because it did not pass
testing, so I bisected to some point. I was about to let you know once
most of 4.9 patches are prepared so there are less merge conflicts.

  reply	other threads:[~2016-09-06 10:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1472990010-10707-1-git-send-email-fxinrong@gmail.com>
2016-09-05  1:19 ` [PATCH] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree Zhao Lei
2016-09-05  7:56   ` Qu Wenruo
2016-09-06  2:41     ` Zhao Lei
2016-09-06  3:05     ` Jeff Mahoney
2016-09-06  3:13       ` Jeff Mahoney
2016-09-06  9:58         ` David Sterba [this message]
2016-09-06 15:12           ` Jeff Mahoney
2016-09-07  1:44             ` Sean Fu
2016-09-09  3:08             ` Sean Fu
2016-09-09  3:25               ` Jeff Mahoney
2016-09-09  3:45                 ` Sean Fu
2016-09-10 15:58                 ` Sean Fu
2016-09-10 16:01                   ` Jeff Mahoney
2016-09-07  1:38     ` Sean Fu
2016-09-07  1:56       ` Qu Wenruo

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=20160906095858.GA16983@suse.cz \
    --to=dsterba@suse.cz \
    --cc=FdManana@suse.com \
    --cc=anand.jain@oracle.com \
    --cc=clm@fb.com \
    --cc=fxinrong@gmail.com \
    --cc=jeffm@suse.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quwenruo@cn.fujitsu.com \
    --cc=zhaolei@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 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).