From: hch@lst.de (Christoph Hellwig)
Subject: draft ANA support v6
Date: Fri, 27 Jul 2018 09:37:43 +0200 [thread overview]
Message-ID: <20180727073743.GB21705@lst.de> (raw)
In-Reply-To: <3ecdfe4c-f3a2-6314-c9da-1d56a6caaf38@suse.de>
On Fri, Jul 27, 2018@08:06:44AM +0200, Hannes Reinecke wrote:
> On 07/26/2018 05:34 PM, Christoph Hellwig wrote:
> > I think we are about ready to merge now, so please review carefully.
> >
> > A git tree is available at:
> >
> > git://git.infradead.org/users/hch/block.git nvme-ana
> >
> > Gitweb:
> >
> > http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/nvme-ana
> >
> Can you please push v6 to the git tree?
> I'm only seeing v5 there ...
Done.
prev parent reply other threads:[~2018-07-27 7:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 15:34 draft ANA support v6 Christoph Hellwig
2018-07-26 15:34 ` [PATCH 1/9] nvme.h: add support for the log specific field Christoph Hellwig
2018-07-26 15:34 ` [PATCH 2/9] nvme.h: add ANA definitions Christoph Hellwig
2018-07-26 15:34 ` [PATCH 3/9] nvme: simplify the API for getting log pages Christoph Hellwig
2018-07-26 15:35 ` [PATCH 4/9] nvme: remove nvme_req_needs_failover Christoph Hellwig
2018-07-26 15:35 ` [PATCH 5/9] nvme: add ANA support Christoph Hellwig
2018-07-26 17:20 ` Mike Snitzer
2018-07-27 13:20 ` Hannes Reinecke
2018-07-27 13:38 ` Mike Snitzer
2018-07-26 15:35 ` [PATCH 6/9] nvmet: keep a port pointer in nvmet_ctrl Christoph Hellwig
2018-07-26 15:35 ` [PATCH 7/9] nvmet: track and limit the number of namespaces per subsystem Christoph Hellwig
2018-07-26 15:35 ` [PATCH 8/9] nvmet: add minimal ANA support Christoph Hellwig
2018-07-26 15:35 ` [PATCH 9/9] nvmet: support configuring ANA groups Christoph Hellwig
2018-07-27 6:06 ` draft ANA support v6 Hannes Reinecke
2018-07-27 7:37 ` 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=20180727073743.GB21705@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).