From: Brendan Hide <brendan@swiftspirit.co.za>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: add btrfs resize unit t/p/e support
Date: Thu, 27 Mar 2014 09:35:41 +0200 [thread overview]
Message-ID: <5333D4CD.6030605@swiftspirit.co.za> (raw)
In-Reply-To: <1395888673-28433-1-git-send-email-guihc.fnst@cn.fujitsu.com>
On 2014/03/27 04:51 AM, Gui Hecheng wrote:
> [snip]
>
> We add t/p/e support by replacing lib/cmdline.c:memparse
> with btrfs_memparse. The btrfs_memparse copies memparse's code
> and add unit t/p/e parsing.
Is there a conflict preventing adding this to memparse directly?
--
__________
Brendan Hide
http://swiftspirit.co.za/
http://www.webafrica.co.za/?AFF1E97
next prev parent reply other threads:[~2014-03-27 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 2:51 [PATCH] btrfs: add btrfs resize unit t/p/e support Gui Hecheng
2014-03-27 2:51 ` [PATCH] btrfs-progs: update manpage for btrfs resize support size unit t/p/e Gui Hecheng
2014-03-27 7:35 ` Brendan Hide [this message]
2014-03-27 15:27 ` [PATCH] btrfs: add btrfs resize unit t/p/e support David Sterba
2014-03-28 1:08 ` Gui Hecheng
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=5333D4CD.6030605@swiftspirit.co.za \
--to=brendan@swiftspirit.co.za \
--cc=guihc.fnst@cn.fujitsu.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