From: Chris Mason <clm@fb.com>
To: Christoph Hellwig <hch@infradead.org>, Miao Xie <miaox@cn.fujitsu.com>
Cc: Christoph Hellwig <hch@infradead.org>, <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs/024 is unhappy on current HEAD
Date: Wed, 11 Dec 2013 10:34:51 -0500 [thread overview]
Message-ID: <20131211153421.7422.45762@ret> (raw)
In-Reply-To: <20131211110007.GA10699@infradead.org>
Quoting Christoph Hellwig (2013-12-11 06:00:07)
> On Wed, Dec 11, 2013 at 06:59:37PM +0800, Miao Xie wrote:
> > This bug has been fixed by
> >
> > https://patchwork.kernel.org/patch/3222061/
>
> Would be good to get it out to Linus ASAP..
My new devel boxes are up and running now, so I'm starting tests for a
pull. It should go out tomorrow.
-chris
prev parent reply other threads:[~2013-12-11 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 10:39 btrfs/024 is unhappy on current HEAD Christoph Hellwig
2013-12-11 10:59 ` Miao Xie
2013-12-11 11:00 ` Christoph Hellwig
2013-12-11 15:34 ` Chris Mason [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=20131211153421.7422.45762@ret \
--to=clm@fb.com \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=miaox@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).