From: Chris Mason <chris.mason@fusionio.com>
To: Miao Xie <miaox@cn.fujitsu.com>
Cc: Linux Btrfs <linux-btrfs@vger.kernel.org>,
Chen Yang <chenyang.fnst@cn.fujitsu.com>
Subject: Re: [RFC][PATCH] Btrfs-progs, btrfsck: add block group check function
Date: Tue, 2 Oct 2012 20:21:56 -0400 [thread overview]
Message-ID: <20121003002156.GI3214@shiny> (raw)
In-Reply-To: <501A530D.2020107@cn.fujitsu.com>
On Thu, Aug 02, 2012 at 04:14:37AM -0600, Miao Xie wrote:
> From: Chen Yang <chenyang.fnst@cn.fujitsu.com>
>
> This patch adds the function to check correspondence between block group,
> chunk and device extent.
Excellent, thank you. Could you please put this into a git tree? I'm
having trouble with whitespace (tabs -> spaces) in the patch.
-chris
next prev parent reply other threads:[~2012-10-03 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 10:14 [RFC][PATCH] Btrfs-progs, btrfsck: add block group check function Miao Xie
2012-10-03 0:21 ` Chris Mason [this message]
2012-10-09 3:46 ` Miao Xie
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=20121003002156.GI3214@shiny \
--to=chris.mason@fusionio.com \
--cc=chenyang.fnst@cn.fujitsu.com \
--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).