From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH 0/7] Few patches extracted from the centralization set
Date: Thu, 29 Jun 2017 12:34:29 -0400 [thread overview]
Message-ID: <20170629163428.GE3110@localhost.localdomain> (raw)
In-Reply-To: <1498734552-14845-1-git-send-email-sagi@grimberg.me>
On Thu, Jun 29, 2017@02:09:05PM +0300, Sagi Grimberg wrote:
> Feedback was that they made sense on their own.
> Plus also few patches that I came up with.
>
> The repetition of patches seem to highlight the fact that we
> will benefit centralization of shared logic.
>
> Sagi Grimberg (7):
> nvme: move queue_count to the nvme_ctrl
> nvme: move ctrl cap to struct nvme_ctrl
> nvme-pci: rename to nvme_pci_configure_admin_queue
> nvme-fc: don't override opts->nr_io_queues
> nvme-rdma: update tagset nr_hw_queues after reconnecting/resetting
> nvme-loop: update tagset nr_hw_queues after reconnecting/resetting
> nvme-fc: update tagset nr_hw_queues after queues reinit
All of these look fine to me.
Reviewed-by: Keith Busch <keith.busch at intel.com>
prev parent reply other threads:[~2017-06-29 16:34 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 11:09 [PATCH 0/7] Few patches extracted from the centralization set Sagi Grimberg
2017-06-29 11:09 ` [PATCH 1/7] nvme: move queue_count to the nvme_ctrl Sagi Grimberg
2017-06-29 11:17 ` Johannes Thumshirn
2017-06-29 13:33 ` Max Gurtovoy
2017-06-29 14:51 ` Christoph Hellwig
2017-06-29 15:03 ` James Smart
2017-07-05 16:23 ` Keith Busch
2017-06-29 11:09 ` [PATCH 2/7] nvme: move ctrl cap to struct nvme_ctrl Sagi Grimberg
2017-06-29 11:18 ` Johannes Thumshirn
2017-06-29 13:36 ` Max Gurtovoy
2017-06-29 14:52 ` Christoph Hellwig
2017-06-29 11:09 ` [PATCH 3/7] nvme-pci: rename to nvme_pci_configure_admin_queue Sagi Grimberg
2017-06-29 11:21 ` Johannes Thumshirn
2017-06-29 13:36 ` Max Gurtovoy
2017-06-29 14:52 ` Christoph Hellwig
2017-07-05 16:23 ` Keith Busch
2017-06-29 11:09 ` [PATCH 4/7] nvme-fc: don't override opts->nr_io_queues Sagi Grimberg
2017-06-29 11:29 ` Johannes Thumshirn
2017-06-29 13:43 ` Max Gurtovoy
2017-06-29 14:52 ` Christoph Hellwig
2017-06-29 15:11 ` James Smart
2017-07-02 8:10 ` Sagi Grimberg
2017-07-03 17:46 ` James Smart
2017-06-29 11:09 ` [PATCH 5/7] nvme-rdma: update tagset nr_hw_queues after reconnecting/resetting Sagi Grimberg
2017-06-29 11:31 ` Johannes Thumshirn
2017-06-29 14:53 ` Christoph Hellwig
2017-06-29 11:09 ` [PATCH 6/7] nvme-loop: " Sagi Grimberg
2017-06-29 11:31 ` Johannes Thumshirn
2017-06-29 14:53 ` Christoph Hellwig
2017-06-29 11:09 ` [PATCH 7/7] nvme-fc: update tagset nr_hw_queues after queues reinit Sagi Grimberg
2017-06-29 11:31 ` Johannes Thumshirn
2017-06-29 14:53 ` Christoph Hellwig
2017-06-29 16:34 ` Keith Busch [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=20170629163428.GE3110@localhost.localdomain \
--to=keith.busch@intel.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 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.