All of lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 00/12] Few more patches from the centralization set
Date: Thu, 10 Aug 2017 10:55:10 +0200	[thread overview]
Message-ID: <20170810085510.GA23011@lst.de> (raw)
In-Reply-To: <1499667759-15965-1-git-send-email-sagi@grimberg.me>

Thanks Sagi,

I've applied the series to the nvme-4.14 branch.

      parent reply	other threads:[~2017-08-10  8:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-10  6:22 [PATCH 00/12] Few more patches from the centralization set Sagi Grimberg
2017-07-10  6:22 ` [PATCH 01/12] nvme-rdma: move nvme_rdma_configure_admin_queue code location Sagi Grimberg
2017-07-10  6:22 ` [PATCH 02/12] nvme: Add admin_tagset pointer to nvme_ctrl Sagi Grimberg
2017-07-10  6:22 ` [PATCH 03/12] nvme-rdma: move tagset allocation to a dedicated routine Sagi Grimberg
2017-07-10  6:22 ` [PATCH 04/12] nvme-rdma: disable the controller on resets Sagi Grimberg
2017-07-10  6:22 ` [PATCH 05/12] nvme-rdma: don't free tagset " Sagi Grimberg
2017-07-10  6:22 ` [PATCH 06/12] nvme-rdma: reuse configure/destroy_admin_queue Sagi Grimberg
2017-07-10  6:22 ` [PATCH 07/12] nvme-rdma: introduce configure/destroy io queues Sagi Grimberg
2017-07-10  6:22 ` [PATCH 08/12] nvme-rdma: stop queues instead of simply flipping their state Sagi Grimberg
2017-07-10  6:22 ` [PATCH 09/12] nvme-rdma: rename nvme_rdma_init_queue to nvme_rdma_alloc_queue Sagi Grimberg
2017-07-10  6:22 ` [PATCH 10/12] nvme-rdma: introduce nvme_rdma_start_queue Sagi Grimberg
2017-07-10  6:22 ` [PATCH 11/12] nvme-rdma: cleanup error path in controller reset Sagi Grimberg
2017-07-10  6:22 ` [PATCH 12/12] nvme-rdma: call ops->reg_read64 instead of nvmf_reg_read64 Sagi Grimberg
2017-08-10  8:55 ` 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=20170810085510.GA23011@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.