xfs
[Top] [All Lists]

Re: [PATCH 18/19] mkfs: unit conversions are case insensitive

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: [PATCH 18/19] mkfs: unit conversions are case insensitive
From: Jan Tulak <jtulak@xxxxxxxxxx>
Date: Thu, 7 Apr 2016 12:50:23 +0200
Cc: xfs-oss <xfs@xxxxxxxxxxx>
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <57057B2A.3000100@xxxxxxxxxxx>
References: <1458818136-56043-1-git-send-email-jtulak@xxxxxxxxxx> <1458818136-56043-19-git-send-email-jtulak@xxxxxxxxxx> <57057B2A.3000100@xxxxxxxxxxx>
On Wed, Apr 6, 2016 at 11:10 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
On 3/24/16 6:15 AM, jtulak@xxxxxxxxxx wrote:
> From: Jan Tulak <jtulak@xxxxxxxxxx>
>
> Solves the question "Should I use 10g or 10G?"

Might be nicer to do it like the cvtnum in libxcmd:

    c = tolower(*sp);
    switch (c) {
    case 'b':
        return i * blocksize;
...
âYeah, changed.
â
Â

(hm, why do we have 3 copies of cvtnum?)

âWhere? â
Ââ

â$ pwd
â/some/path/xfsprogs-dev

$ grep -r "cvtnum(size_t" . |grep -v "^Binary"
â./include/input.h:extern long long cvtnum(size_t blocksize, size_t sectorsize, char *s);
./io/init.h:extern void init_cvtnum(size_t *blocksize, size_t *sectsize);

--
<Prev in Thread] Current Thread [Next in Thread>