From: Johannes Thumshirn <Johannes.Thumshirn@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>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH rfc 1/6] nvme: consolidate nvme requirements based on transport type
Date: Mon, 3 Aug 2020 07:13:22 +0000 [thread overview]
Message-ID: <SN4PR0401MB35985B07784F73DD9C27BC879B4D0@SN4PR0401MB3598.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200803064835.67927-2-sagi@grimberg.me
Looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-08-03 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:48 [PATCH rfc 0/6] blktests: Add support to run nvme tests with tcp/rdma transports Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 1/6] nvme: consolidate nvme requirements based on transport type Sagi Grimberg
2020-08-03 7:13 ` Johannes Thumshirn [this message]
2020-08-03 6:48 ` [PATCH rfc 2/6] nvme: consolidate some nvme-cli utility functions Sagi Grimberg
2020-08-03 7:12 ` Johannes Thumshirn
2020-08-03 6:48 ` [PATCH rfc 3/6] nvme: make tests transport type agnostic Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 4/6] tests/nvme: restrict tests to specific transports Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 5/6] nvme: support nvme-tcp when runinng tests Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 6/6] nvme: support rdma transport type Sagi Grimberg
2020-08-05 8:57 ` Yi Zhang
2020-08-05 17:59 ` Sagi Grimberg
2020-08-03 20:16 ` [PATCH rfc 0/6] blktests: Add support to run nvme tests with tcp/rdma transports Chaitanya Kulkarni
2020-08-04 15:37 ` Sagi Grimberg
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=SN4PR0401MB35985B07784F73DD9C27BC879B4D0@SN4PR0401MB3598.namprd04.prod.outlook.com \
--to=johannes.thumshirn@wdc.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.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).