From: hch@lst.de (Christoph Hellwig)
Subject: dusted off ANA code
Date: Mon, 14 May 2018 10:57:59 +0200 [thread overview]
Message-ID: <20180514085759.GA21502@lst.de> (raw)
In-Reply-To: <20180514101117.5b536b6b@pentland.suse.de>
On Mon, May 14, 2018@10:11:17AM +0200, Hannes Reinecke wrote:
> I'll be working on integrating both codestreams and send a combined
> patchset for review.
>
> Unless you want to do it yourself ...
Please go ahead, I'm completely overloaded at the moment anyway.
prev parent reply other threads:[~2018-05-14 8:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-14 7:56 dusted off ANA code Christoph Hellwig
2018-05-14 7:56 ` [PATCH 01/11] nvme.h: untangle AEN notice definitions Christoph Hellwig
2018-05-14 7:56 ` [PATCH 02/11] nvme.h: add ANA definitions Christoph Hellwig
2018-05-14 7:56 ` [PATCH 03/11] nvme: add support for the log specific field Christoph Hellwig
2018-05-14 7:56 ` [PATCH 04/11] nvme: always failover on path or transport errors Christoph Hellwig
2018-05-14 7:56 ` [PATCH 05/11] nvme: add ANA support Christoph Hellwig
2018-05-14 7:56 ` [PATCH 06/11] nvmet: refactor AER handling Christoph Hellwig
2018-05-14 7:56 ` [PATCH 07/11] nvmet: add a new nvmet_zero_sgl helper Christoph Hellwig
2018-05-14 7:56 ` [PATCH 08/11] nvmet: split log page implementation Christoph Hellwig
2018-05-14 7:56 ` [PATCH 09/11] nvmet: track and limit the number of namespaces per subsystem Christoph Hellwig
2018-05-14 7:56 ` [PATCH 10/11] nvmet: add minimal ANA support Christoph Hellwig
2018-05-14 7:56 ` [PATCH 11/11] nvmet: support configuring additional ANA groups Christoph Hellwig
2018-05-14 8:09 ` dusted off ANA code Hannes Reinecke
2018-05-14 8:11 ` Hannes Reinecke
2018-05-14 8:57 ` 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=20180514085759.GA21502@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.