From: Eric Sandeen <sandeen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Josef Bacik <josef@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] fiemap tester
Date: Mon, 11 May 2009 10:14:55 -0500 [thread overview]
Message-ID: <4A0840EF.6020601@redhat.com> (raw)
In-Reply-To: <20090511094639.GA7488@infradead.org>
Christoph Hellwig wrote:
> On Fri, May 08, 2009 at 04:13:18PM -0700, Andrew Morton wrote:
>> 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.
>
> Why oh why do people think Documentation/ is a good place for code?
>
> tests/ would be a much better place :)
>
> Last time I brought the idea of a small in-tree test harness up at KS
> people weren't too fond of it, but if we get more backing now we could
> try it, otherwise we can just stick it into xfsqa which will hopefully
> soon be generalized to a general fs QA suite.
FWIW, the xfsprogs test suite git tree is currently at 11M; and that's
mostly just for one subtype of one subsystem. Aiming to have a full
kernel test suite in the kernel tree sounds lke it could get unwieldy to
me...
I'll stick this new test into xfstests regardless, for now...
-Eric
next prev parent reply other threads:[~2009-05-11 15: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
2009-05-11 9:46 ` Christoph Hellwig
2009-05-11 15:14 ` Eric Sandeen [this message]
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=4A0840EF.6020601@redhat.com \
--to=sandeen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=josef@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).