From: Christoph Hellwig <hch@lst.de>
To: Max Gurtovoy <maxg@mellanox.com>
Cc: bvanassche@acm.org, linux-nvme@lists.infradead.org,
shlomin@mellanox.com, jgg@mellanox.com, kbusch@kernel.org,
hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH v4 1/1] nvmet-rdma: use SRQ per completion vector
Date: Wed, 1 Apr 2020 10:33:01 +0200 [thread overview]
Message-ID: <20200401083301.GA30082@lst.de> (raw)
In-Reply-To: <20200326181512.58053-1-maxg@mellanox.com>
Applied to nvme-5.8.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2020-04-01 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 18:15 [PATCH v4 1/1] nvmet-rdma: use SRQ per completion vector Max Gurtovoy
2020-03-26 18:29 ` Laurence Oberman
2020-03-26 22:14 ` Max Gurtovoy
2020-03-26 23:20 ` Sagi Grimberg
2020-03-27 0:44 ` Max Gurtovoy
2020-03-31 14:43 ` Max Gurtovoy
2020-03-31 15:06 ` Christoph Hellwig
2020-04-01 8:33 ` Christoph Hellwig [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=20200401083301.GA30082@lst.de \
--to=hch@lst.de \
--cc=bvanassche@acm.org \
--cc=jgg@mellanox.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=maxg@mellanox.com \
--cc=sagi@grimberg.me \
--cc=shlomin@mellanox.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).