From: hch@lst.de (Christoph Hellwig)
Subject: Q: Status of ANA patches
Date: Tue, 17 Jul 2018 15:50:07 +0200 [thread overview]
Message-ID: <20180717135007.GA17263@lst.de> (raw)
In-Reply-To: <01b035fe-72cb-72c8-daa4-00d416815550@suse.de>
On Tue, Jul 17, 2018@03:42:06PM +0200, Hannes Reinecke wrote:
> So, just submitted a blktest to check the basic functionality via
> nvme-loop, including path failover.
Thanks!
> And send some fixes for issues found during development of the said test :-)
Yes, that's why we need tests.
>
> If you can think of anything else which should be tested please let me
> know, I'm happy to write up a testcase for that.
>
> But what's next, then?
> Will you fold the patches into the main patchset?
> Or should they be kept separate?
> Should I be doing it (if you are too busy)?
Pretty busy this week, so for now just send incremental patches if needed.
I'll try to fold your fixes, try the test suite (and maybe add some
of the bits I did test manually to it) and prepare a merge candidate
for next week.
next prev parent reply other threads:[~2018-07-17 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 11:42 Q: Status of ANA patches Hannes Reinecke
2018-06-29 12:03 ` Christoph Hellwig
2018-07-17 13:42 ` Hannes Reinecke
2018-07-17 13:50 ` Christoph Hellwig [this message]
2018-07-19 14:28 ` Christoph Hellwig
2018-07-25 0:50 ` Chaitanya Kulkarni
2018-07-25 5:05 ` Christoph Hellwig
2018-07-26 9:24 ` Johannes Thumshirn
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=20180717135007.GA17263@lst.de \
--to=hch@lst.de \
/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).