From: Johannes Thumshirn <jthumshirn@suse.de>
To: bingjingc <bingjingc@synology.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, cccheng@synology.com,
linux-raid@vger.kernel.org
Subject: Re: [PATCH blktests 1/9] blktests: add hepler functions for new md tests
Date: Thu, 7 Jun 2018 08:55:24 +0200 [thread overview]
Message-ID: <20180607065524.kohrpiskf4wfhl3t@linux-x5ow.site> (raw)
In-Reply-To: <c55cae7e78b069afe98cb5e485fe67b1@synology.com>
On Thu, Jun 07, 2018 at 10:45:02AM +0800, bingjingc wrote:
> Hi Johannes & Jens,
>
> Thank you for your information and positive feedbacks on this patch.
>
> I'm also inspired by xfstests, too. Most conventional filesystems
> have their test cases on it. I believe block layer can also have one.
>
> I felt sorry. It's first time I realized there is a test suite under
> mdadm project. Now, I am trying to find documentation to get
> it works. I can examine the efforts of migrating them or just
> triggering them from blktests.
>
> Any ideas from linux-block and linux-raid channels are welcome. :)
Migrating them over would be the best thing since sliced bread. Having
to run only one test suite for the linux block device space is our
long term goal.
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn@suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N�rnberg
GF: Felix Imend�rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N�rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-06-07 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 8:06 [PATCH blktests 1/9] blktests: add hepler functions for new md tests bingjingc
2018-06-06 8:44 ` Johannes Thumshirn
2018-06-06 14:29 ` Jens Axboe
2018-06-06 14:33 ` Johannes Thumshirn
2018-06-07 2:45 ` bingjingc
2018-06-07 6:55 ` Johannes Thumshirn [this message]
2018-06-07 12:59 ` Jens Axboe
2018-06-08 14:50 ` Wols Lists
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=20180607065524.kohrpiskf4wfhl3t@linux-x5ow.site \
--to=jthumshirn@suse.de \
--cc=axboe@kernel.dk \
--cc=bingjingc@synology.com \
--cc=cccheng@synology.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@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