public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: bingjingc <bingjingc@synology.com>
To: Johannes Thumshirn <jthumshirn@suse.de>
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, 07 Jun 2018 10:45:02 +0800	[thread overview]
Message-ID: <c55cae7e78b069afe98cb5e485fe67b1@synology.com> (raw)
In-Reply-To: <20180606143307.p7puz56rdcgyk4se@linux-x5ow.site>

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. :)

All the best,
BingJing

Johannes Thumshirn 於 2018-06-06 22:33 寫到:
> On Wed, Jun 06, 2018 at 08:29:25AM -0600, Jens Axboe wrote:
>> Hopefully this can be the start of migrating over those tests!
> 
> Yes this would be great. I just wanted to connect the submitter and
> the md developers and make them aware of possibly duplicated efforts
> ;-).

  reply	other threads:[~2018-06-07  2:45 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 [this message]
2018-06-07  6:55         ` Johannes Thumshirn
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=c55cae7e78b069afe98cb5e485fe67b1@synology.com \
    --to=bingjingc@synology.com \
    --cc=axboe@kernel.dk \
    --cc=cccheng@synology.com \
    --cc=jthumshirn@suse.de \
    --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