linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <jbacik@fusionio.com>
Cc: Anand Jain <Anand.Jain@oracle.com>,
	dsterba@suse.cz, linux-btrfs@vger.kernel.org,
	chris.mason@fusionio.com
Subject: Re: [PATCH 1/3 v4] btrfs-progs: use kernel for mounted disk for show
Date: Tue, 22 Oct 2013 18:52:33 +0200	[thread overview]
Message-ID: <20131022165233.GA1032@twin.jikos.cz> (raw)
In-Reply-To: <20131022132147.GA27304@localhost.localdomain>

On Tue, Oct 22, 2013 at 09:21:47AM -0400, Josef Bacik wrote:
> Did you test these?  Because they aren't working for me, so I think a revert is
> the only solution.  Thanks,

The impact of the failing test is imho not that big to justify a full
revert from integration branch (were it in master, then yes). I see the
bug and I hope Anand will fix it soon.

david

  parent reply	other threads:[~2013-10-22 16:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08  3:41 [PATCH 1/3 v4] btrfs-progs: use kernel for mounted disk for show Anand Jain
2013-10-08  3:41 ` [PATCH 2/3 v2] btrfs-progs: add more parameter to the filesystem show Anand Jain
2013-10-15 17:22   ` David Sterba
2013-10-16  2:22     ` Anand Jain
2013-10-08  3:41 ` [PATCH 3/3] btrfs-progs: use BTRFS_SCAN_LBLKID as default scan in " Anand Jain
2013-10-15 17:13 ` [PATCH 1/3 v4] btrfs-progs: use kernel for mounted disk for show David Sterba
2013-10-16  9:25   ` Anand Jain
2013-10-16 13:09     ` David Sterba
2013-10-21 14:44   ` Josef Bacik
2013-10-22  5:53     ` Anand Jain
2013-10-22 13:21       ` Josef Bacik
2013-10-22 13:28         ` Hugo Mills
2013-10-22 16:52         ` David Sterba [this message]
2013-10-23 11:20           ` Anand Jain
2013-10-23 11:41             ` Anand Jain

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=20131022165233.GA1032@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=Anand.Jain@oracle.com \
    --cc=chris.mason@fusionio.com \
    --cc=jbacik@fusionio.com \
    --cc=linux-btrfs@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).