From: Omar Sandoval <osandov@osandov.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Omar Sandoval <osandov@fb.com>,
linux-block@vger.kernel.org,
Johannes Thumshirn <jthumshirn@suse.de>,
Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [PATCH blktests 0/4] Four blktests patches
Date: Wed, 4 Sep 2019 10:55:15 -0700 [thread overview]
Message-ID: <20190904175515.GD7452@vader> (raw)
In-Reply-To: <2e2e3abb-1420-7743-eb7f-cd9744d36686@acm.org>
On Wed, Sep 04, 2019 at 10:49:13AM -0700, Bart Van Assche wrote:
> On 8/8/19 1:05 PM, Bart Van Assche wrote:
> > Hi Omar,
> >
> > This series includes one improvement for the NVMe tests, two improvements for
> > the NVMeOF-multipath tests and version two of the SRP test that triggers a SCSI
> > reset while I/O is ongoing. Please consider these for the official blktests
> > git repository.
>
> (replying to my own e-mail)
>
> Hi Omar,
>
> This patch series was posted about one month ago. Feedback about how to
> proceed with this patch series is still welcome.
I was actually just in the middle of merging it. Pushed now, thanks and
sorry for the delay.
prev parent reply other threads:[~2019-09-04 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 20:05 [PATCH blktests 0/4] Four blktests patches Bart Van Assche
2019-08-08 20:05 ` [PATCH blktests 1/4] tests/nvme/rc: Modify the approach for disabling and re-enabling Ctrl-C Bart Van Assche
2019-08-08 20:08 ` Logan Gunthorpe
2019-08-08 21:00 ` Bart Van Assche
2019-08-08 21:11 ` Logan Gunthorpe
2019-08-08 21:18 ` Bart Van Assche
2019-08-08 20:05 ` [PATCH blktests 2/4] tests/nvmeof-mp/rc: Make simulate_network_failure_loop() more robust Bart Van Assche
2019-08-08 20:05 ` [PATCH blktests 3/4] tests/nvmeof-mp/rc: Make the NVMeOF multipath tests more reliable Bart Van Assche
2019-08-08 20:05 ` [PATCH blktests 4/4] tests/srp/014: Add a test that triggers a SCSI reset while I/O is ongoing Bart Van Assche
2019-09-04 17:49 ` [PATCH blktests 0/4] Four blktests patches Bart Van Assche
2019-09-04 17:55 ` Omar Sandoval [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=20190904175515.GD7452@vader \
--to=osandov@osandov.com \
--cc=bvanassche@acm.org \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=osandov@fb.com \
/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).