public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs mailing list <xfs@oss.sgi.com>
Subject: Re: [PATCH 0/3 v4]  hook xfs to fiemap ioctl
Date: Wed, 12 Nov 2008 07:33:57 -0600	[thread overview]
Message-ID: <491ADB45.9070301@sandeen.net> (raw)
In-Reply-To: <20081112092340.GE8896@infradead.org>

Christoph Hellwig wrote:
> On Wed, Oct 29, 2008 at 11:55:50AM -0500, Eric Sandeen wrote:
>> Also, here's a very hacky (don't laugh!) test app.  I'll clean it
>> up at some point   :)  
>>
>> (v4: test app slightly more cleaned up)
> 
> Can you wire up the test program to xfsqa?  Also instead of having your
> own #defines for the constants just use a copy of fiemap.h?
> 

Sure, that makes sense.

I'm not sure how to best exercise fiemap in xfsqa... I guess I should
look to see if there are any xfs_bmap checkers in there and model on that.

-Eric

      reply	other threads:[~2008-11-12 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 16:55 [PATCH 0/3 v4] hook xfs to fiemap ioctl Eric Sandeen
2008-10-29 16:58 ` [PATCH 1/3 v4] convert xfs_getbmap to take formatter functions Eric Sandeen
2008-11-12  9:21   ` Christoph Hellwig
2008-10-29 16:58 ` [PATCH 2/3 v4] Add new flags to getbmapx interface Eric Sandeen
2008-11-12  9:22   ` Christoph Hellwig
2008-10-29 16:59 ` [PATCH 3/3 v4] hook up fiemap & associated formatter Eric Sandeen
2008-11-12  9:22   ` Christoph Hellwig
2008-11-19  4:59   ` Eric Sandeen
2008-11-12  9:23 ` [PATCH 0/3 v4] hook xfs to fiemap ioctl Christoph Hellwig
2008-11-12 13:33   ` Eric Sandeen [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=491ADB45.9070301@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.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