From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Johannes Thumshirn <jthumshirn@suse.de>,
Eric Sandeen <sandeen@sandeen.net>,
Christoph Hellwig <hch@infradead.org>,
Dmitry Monakhov <dmonakhov@openvz.org>,
fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH 0/6] RFC add blkdev tests v2
Date: Thu, 6 Apr 2017 11:22:52 -0700 [thread overview]
Message-ID: <20170406182252.GA31688@infradead.org> (raw)
In-Reply-To: <b58871ff-2b34-acce-318c-479dccf4d596@kernel.dk>
On Thu, Apr 06, 2017 at 12:19:46PM -0600, Jens Axboe wrote:
> We share that goal. The block related tests will have _fewer_ dependencies.
> And it'll also be Linux only, so we don't have to worry about cross platform.
xfstests effectively has been Linux-only for many years. We've just
been to lazy to remove the remaining IRIX bits..
prev parent reply other threads:[~2017-04-06 18:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 13:19 [PATCH 0/6] RFC add blkdev tests v2 Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 1/6] add lio-target helpers Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 2/6] add: blockdev/001 check page-cache coherency after BLKDISCARD Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 3/6] new: blockdev/002 check information leak for lio-fileio Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 4/6] new: blockdev/003 basic blockdev T10-DIF-TYPE1 integrity checks Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 5/6] new: blockdev/004 Check that live fs survives blkdev page truncation Dmitry Monakhov
2017-04-06 13:19 ` [PATCH 6/6] new: blockdev/005 Check that busy " Dmitry Monakhov
2017-04-06 13:55 ` [PATCH 0/6] RFC add blkdev tests v2 Christoph Hellwig
2017-04-06 14:33 ` Jens Axboe
2017-04-06 14:47 ` Christoph Hellwig
2017-04-06 14:51 ` Jens Axboe
2017-04-06 15:20 ` Johannes Thumshirn
2017-04-06 15:32 ` Eric Sandeen
2017-04-06 18:15 ` Johannes Thumshirn
2017-04-06 18:19 ` Jens Axboe
2017-04-06 18:22 ` Christoph Hellwig [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=20170406182252.GA31688@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=dmonakhov@openvz.org \
--cc=fstests@vger.kernel.org \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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).