From: Omar Sandoval <osandov@osandov.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: linux-block@vger.kernel.org,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Omar Sandoval <osandov@fb.com>,
linux-nvme@lists.infradead.org, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH blktests v3] nvme/031: Add test to check controller deletion after setup
Date: Tue, 15 Oct 2019 16:08:49 -0700 [thread overview]
Message-ID: <20191015230849.GA483958@vader> (raw)
In-Reply-To: <20190911172021.5760-1-logang@deltatee.com>
On Wed, Sep 11, 2019 at 11:20:21AM -0600, Logan Gunthorpe wrote:
> A number of bug fixes have been submitted to the kernel to
> fix bugs when a controller is removed immediately after it is
> set up. This new test ensures this doesn't regress.
>
> Signed-off-by: Logan Gunthorpe <logang@deltatee.com>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
> ---
>
> Changes for v3:
> * Drops the double loop_dev declaration (per Chaitanya)
> * Collected Sagi's reviewed-by tag
>
> tests/nvme/031 | 54 ++++++++++++++++++++++++++++++++++++++++++++++
> tests/nvme/031.out | 2 ++
> 2 files changed, 56 insertions(+)
> create mode 100755 tests/nvme/031
> create mode 100644 tests/nvme/031.out
Thanks, applied.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-10-15 23:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 17:20 [PATCH blktests v3] nvme/031: Add test to check controller deletion after setup Logan Gunthorpe
2019-09-11 20:38 ` Chaitanya Kulkarni
2019-10-15 23:08 ` 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=20191015230849.GA483958@vader \
--to=osandov@osandov.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.com \
--cc=osandov@fb.com \
--cc=sagi@grimberg.me \
/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