public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH 1/2] convert xfs_getbmap to take formatter functions
Date: Fri, 24 Oct 2008 10:35:39 +1100	[thread overview]
Message-ID: <20081023233538.GG18495@disturbed> (raw)
In-Reply-To: <490103C9.9080900@sandeen.net>

On Thu, Oct 23, 2008 at 06:07:53PM -0500, Eric Sandeen wrote:
> Preliminary work to hook up fiemap, this allows us to pass in an
> arbitrary formatter to copy extent data back to userspace.

Is there a fiemap test program around anywhere?

If so, would it be appropriate to include it in xfstests and write
a quick regression test for it? We'd probably need to also check
xfs_bmap gives the same output as fiemap....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2008-10-23 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 23:07 [PATCH 1/2] convert xfs_getbmap to take formatter functions Eric Sandeen
2008-10-23 23:35 ` Dave Chinner [this message]
2008-10-24  0:44   ` Eric Sandeen

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=20081023233538.GG18495@disturbed \
    --to=david@fromorbit.com \
    --cc=sandeen@sandeen.net \
    --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