From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: fstests@vger.kernel.org
Subject: Re: fstests: fix fsx fallocate error messages
Date: Mon, 14 Nov 2016 10:13:59 +1100 [thread overview]
Message-ID: <20161113231359.GK28922@dastard> (raw)
In-Reply-To: <20161112164849.GB18127@infradead.org>
On Sat, Nov 12, 2016 at 08:48:49AM -0800, Christoph Hellwig wrote:
> Many of the commands using fallocate had an extra % at the beggining
> of the error messages, missed the 0x prefix for hex output and printed
> the length where it should print the end of the region.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
looks fine.
Reviewed-by: Dave Chinner <dchinner@redhat.com>
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2016-11-13 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-12 16:48 fstests: fix fsx fallocate error messages Christoph Hellwig
2016-11-13 23:13 ` Dave Chinner [this message]
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=20161113231359.GK28922@dastard \
--to=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=hch@infradead.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