From: Alex Elder <aelder@sgi.com>
To: Allison Henderson <achender@linux.vnet.ibm.com>
Cc: <linux-ext4@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<xfs@oss.sgi.com>
Subject: Re: [PATCH 1/1] XFS TESTS: Correct extent flag parsing for punch hole tests
Date: Fri, 15 Jul 2011 08:46:54 -0500 [thread overview]
Message-ID: <1310737614.2921.4.camel@doink> (raw)
In-Reply-To: <1310701933-18988-1-git-send-email-achender@linux.vnet.ibm.com>
On Thu, 2011-07-14 at 20:52 -0700, Allison Henderson wrote:
> The fiemap filters used in the punch hole tests parse the
> extent flags in the fiemap to determine the extent type.
> They are currently parsing them as decimal values, but
> they should be parsing hex values.
>
> Signed-off-by: Allison Henderson <achender@linux.vnet.ibm.com>
Looks good to me. This may not have a practical
effect but it looks correct now.
I will commit this for you. Thanks for fixing it.
Reviewed-by: Alex Elder <aelder@sgi.com>
prev parent reply other threads:[~2011-07-15 13:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 3:52 [PATCH 1/1] XFS TESTS: Correct extent flag parsing for punch hole tests Allison Henderson
2011-07-15 13:46 ` Alex Elder [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=1310737614.2921.4.camel@doink \
--to=aelder@sgi.com \
--cc=achender@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).