From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Gui Hecheng <guihc.fnst@cn.fujitsu.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: Documentation: add T/P/E description for resize cmd
Date: Mon, 22 Dec 2014 12:20:30 +0900 [thread overview]
Message-ID: <54978DFE.6010507@jp.fujitsu.com> (raw)
In-Reply-To: <1419213702-3945-1-git-send-email-guihc.fnst@cn.fujitsu.com>
On 2014/12/22 11:01, Gui Hecheng wrote:
> Signed-off-by: Gui Hecheng <guihc.fnst@cn.fujitsu.com>
> ---
> Documentation/btrfs-filesystem.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/btrfs-filesystem.txt b/Documentation/btrfs-filesystem.txt
> index a8f2972..f2bd50d 100644
> --- a/Documentation/btrfs-filesystem.txt
> +++ b/Documentation/btrfs-filesystem.txt
> @@ -102,8 +102,8 @@ If the prefix + or - is present the size is increased or decreased
> by the quantity <size>.
> If no units are specified, the unit of the <size> parameter defaults to
> bytes. Optionally, the size parameter may be suffixed by one of the following
> -units designators: \'K\', \'M', or \'G', kilobytes, megabytes, or gigabytes,
> -respectively.
> +units designators: \'K\'(KiB), \'M\'(MiB), \'G\'(GiB), \'T\'(TiB), \'P\'(PiB),
> +\'E\'(EiB).
Just a minor point. s/\'E\'(EiB)/or \'E\'(EiB)/ is better.
Reviewed-by: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
Thanks,
Satoru
> +
> If \'max' is passed, the filesystem will occupy all available space on the
> device devid.
>
next prev parent reply other threads:[~2014-12-22 3:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 2:01 [PATCH] btrfs-progs: Documentation: add T/P/E description for resize cmd Gui Hecheng
2014-12-22 3:20 ` Satoru Takeuchi [this message]
2014-12-22 7:22 ` [PATCH v2] " Gui Hecheng
2014-12-29 16:07 ` David Sterba
2014-12-30 1:23 ` Gui Hecheng
2014-12-30 1:52 ` [PATCH v3] " Gui Hecheng
2015-01-02 3:27 ` Chris Murphy
2015-01-02 16:12 ` David Sterba
2015-01-02 16:21 ` David Sterba
2015-01-05 1:42 ` 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=54978DFE.6010507@jp.fujitsu.com \
--to=takeuchi_satoru@jp.fujitsu.com \
--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;
as well as URLs for NNTP newsgroup(s).