From: keith.busch@intel.com (Keith Busch)
Subject: draft ANA support v5
Date: Tue, 24 Jul 2018 09:56:13 -0600 [thread overview]
Message-ID: <20180724155613.GA13089@localhost.localdomain> (raw)
In-Reply-To: <20180724115009.731-1-hch@lst.de>
On Tue, Jul 24, 2018@01:50:00PM +0200, Christoph Hellwig wrote:
> I think we are about ready to merge now, so please review carefully.
These all look good to me. For the series:
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2018-07-24 15:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 11:50 draft ANA support v5 Christoph Hellwig
2018-07-24 11:50 ` [PATCH 1/9] nvme.h: add support for the log specific field Christoph Hellwig
2018-07-24 11:50 ` [PATCH 2/9] nvme.h: add ANA definitions Christoph Hellwig
2018-07-25 0:24 ` Chaitanya Kulkarni
2018-07-25 4:58 ` Christoph Hellwig
2018-07-24 11:50 ` [PATCH 3/9] nvme: simplify the API for getting log pages Christoph Hellwig
2018-07-24 11:50 ` [PATCH 4/9] nvme: remove nvme_req_needs_failover Christoph Hellwig
2018-07-24 11:50 ` [PATCH 5/9] nvme: add ANA support Christoph Hellwig
2018-07-26 2:00 ` Martin K. Petersen
2018-07-26 11:34 ` Johannes Thumshirn
2018-07-24 11:50 ` [PATCH 6/9] nvmet: keep a port pointer in nvmet_ctrl Christoph Hellwig
2018-07-26 11:34 ` Johannes Thumshirn
2018-07-24 11:50 ` [PATCH 7/9] nvmet: track and limit the number of namespaces per subsystem Christoph Hellwig
2018-07-24 11:50 ` [PATCH 8/9] nvmet: add minimal ANA support Christoph Hellwig
2018-07-26 11:34 ` Johannes Thumshirn
2018-07-24 11:50 ` [PATCH 9/9] nvmet: support configuring ANA groups Christoph Hellwig
2018-07-26 11:34 ` Johannes Thumshirn
2018-07-24 15:56 ` Keith Busch [this message]
2018-07-26 2:02 ` draft ANA support v5 Martin K. Petersen
2018-07-26 7:45 ` Hannes Reinecke
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=20180724155613.GA13089@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 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).