From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Omar Sandoval <osandov@osandov.com>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH v3 5/7] nvme: support nvme-tcp when runinng tests
Date: Thu, 13 Aug 2020 02:42:13 +0000 [thread overview]
Message-ID: <BYAPR04MB496539E26CFCC0A17C55B4FE86430@BYAPR04MB4965.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200811210102.194287-6-sagi@grimberg.me
On 8/11/20 14:01, Sagi Grimberg wrote:
> run with: nvme_trtype=tcp ./check test/nvme
>
> Signed-off-by: Sagi Grimberg<sagi@grimberg.me>
This patch looks good to me.
Reviwed-by: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
next prev parent reply other threads:[~2020-08-13 2:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 21:00 [PATCH v3 0/7] blktests: Add support to run nvme tests with tcp/rdma transports Sagi Grimberg
2020-08-11 21:00 ` [PATCH v3 1/7] nvme: consolidate nvme requirements based on transport type Sagi Grimberg
2020-08-13 2:44 ` Chaitanya Kulkarni
2020-08-11 21:00 ` [PATCH v3 2/7] nvme: consolidate some nvme-cli utility functions Sagi Grimberg
2020-08-12 15:49 ` Logan Gunthorpe
2020-08-11 21:00 ` [PATCH v3 3/7] nvme: make tests transport type agnostic Sagi Grimberg
2020-08-11 21:00 ` [PATCH v3 4/7] tests/nvme: restrict tests to specific transports Sagi Grimberg
2020-08-11 21:01 ` [PATCH v3 5/7] nvme: support nvme-tcp when runinng tests Sagi Grimberg
2020-08-13 2:42 ` Chaitanya Kulkarni [this message]
2020-08-11 21:01 ` [PATCH v3 6/7] common: move module_unload to common Sagi Grimberg
2020-08-11 21:30 ` Bart Van Assche
2020-08-11 21:45 ` Sagi Grimberg
2020-08-11 21:01 ` [PATCH v3 7/7] nvme: support rdma transport type Sagi Grimberg
2020-08-13 11:01 ` [PATCH v3 0/7] blktests: Add support to run nvme tests with tcp/rdma transports Yi Zhang
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=BYAPR04MB496539E26CFCC0A17C55B4FE86430@BYAPR04MB4965.namprd04.prod.outlook.com \
--to=chaitanya.kulkarni@wdc.com \
--cc=bvanassche@acm.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).