From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: James Lawrie <james@jdlawrie.co.uk>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] xfsprogs: check for size parsing errors in xfs_quota
Date: Tue, 24 Jan 2012 11:58:12 -0600 [thread overview]
Message-ID: <4F1EF134.7000808@redhat.com> (raw)
In-Reply-To: <20120124175612.GH9853@infradead.org>
On 1/24/12 11:56 AM, Christoph Hellwig wrote:
>> - v = (__uint64_t)cvtnum(blocksize, sectorsize, s);
>> - *value = v >> 9; /* syscalls use basic blocks */
>> + v = cvtnum(blocksize, sectorsize, s);
>> + if (v == -1LL) {
>> + fprintf(stderr, _("%s: Error: could not parse size %s.\n"), progname, s);
>> + return 0;
>> + }
>> + *value = (__uint64_t)v >> 8; /* syscalls use basic blocks */
>
> Why do you replace the shift by nine with a shift by 8?
yeargh, NFI - vi gone wild?
> Also please don't introduce new overly long lines, just move the
> translated string to a line of its own, indented by a single tab similar
> to how we do it in most new xfs/xfsprogs code.
Ok, sure, sorry. TBH I noticed it but there was such a long line below
I didn't worry. Will resend.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-24 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 17:31 [PATCH] xfsprogs: check for size parsing errors in xfs_quota Eric Sandeen
2012-01-23 19:59 ` Christoph Hellwig
2012-01-24 5:07 ` Eric Sandeen
2012-01-24 17:56 ` Christoph Hellwig
2012-01-24 17:58 ` Eric Sandeen [this message]
2012-01-27 19:26 ` [PATCH V2] " Eric Sandeen
2012-02-03 17:41 ` Mark Tinguely
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=4F1EF134.7000808@redhat.com \
--to=sandeen@redhat.com \
--cc=hch@infradead.org \
--cc=james@jdlawrie.co.uk \
--cc=xfs@oss.sgi.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