From: Andrew Morton <akpm@linux-foundation.org>
To: Josef Bacik <josef@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, sandeen@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] fiemap tester
Date: Fri, 8 May 2009 16:13:18 -0700 [thread overview]
Message-ID: <20090508161318.c73d766c.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090508191649.GG9068@unused.rdu.redhat.com>
On Fri, 8 May 2009 15:16:49 -0400
Josef Bacik <josef@redhat.com> wrote:
> Here is small little program which I and Eric have been working on this week to
> better test FIEMAP
I for one wouldn't complain were someone to create
Documentation/fs/tests/ and to then start filling it with stuff.
next prev parent reply other threads:[~2009-05-08 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 19:16 [RFC] fiemap tester Josef Bacik
2009-05-08 23:13 ` Andrew Morton [this message]
2009-05-11 9:46 ` Christoph Hellwig
2009-05-11 15:14 ` Eric Sandeen
2009-05-11 17:10 ` Theodore Tso
2009-05-11 17:46 ` Eric Sandeen
2009-05-11 17:54 ` Randy Dunlap
2009-05-11 19:30 ` Theodore Tso
2009-05-11 17:13 ` Andrew Morton
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=20090508161318.c73d766c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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).