From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/1] nvme-rdma: Introduce nvme_rdma_configure_blk/nvme_rdma_destroy_blk
Date: Wed, 8 Nov 2017 19:17:54 +0100 [thread overview]
Message-ID: <20171108181754.GA471@lst.de> (raw)
In-Reply-To: <1510060989-10391-1-git-send-email-maxg@mellanox.com>
On Tue, Nov 07, 2017@03:23:09PM +0200, Max Gurtovoy wrote:
> Create new helpers to avoid code and logic duplication between admin/IO
> block layer resources creation and destruction.
How is this going to interact with Sagi's refactoring in this area?
next prev parent reply other threads:[~2017-11-08 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 13:23 [PATCH 1/1] nvme-rdma: Introduce nvme_rdma_configure_blk/nvme_rdma_destroy_blk Max Gurtovoy
2017-11-08 18:17 ` Christoph Hellwig [this message]
2017-11-12 17:43 ` Max Gurtovoy
2017-11-13 20:27 ` Sagi Grimberg
2017-11-13 20:25 ` 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=20171108181754.GA471@lst.de \
--to=hch@lst.de \
/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).