From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH V3] nvme: fix multiple ctrl removal scheduling
Date: Sun, 28 May 2017 11:40:43 +0200 [thread overview]
Message-ID: <20170528094043.GA14199@lst.de> (raw)
In-Reply-To: <20170526201351.GA21847@dhcp-216.srv.tuxera.com>
Hi Rkesh,
this looks reasonable, but we'll need to also adopt the non-PCI
driver to the new state machine. I can give this a spin.
At that point we probably want to move nvme_reset into common
code somehow.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Rakesh Pandit <rakesh@tuxera.com>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Keith Busch <keith.busch@intel.com>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH V3] nvme: fix multiple ctrl removal scheduling
Date: Sun, 28 May 2017 11:40:43 +0200 [thread overview]
Message-ID: <20170528094043.GA14199@lst.de> (raw)
In-Reply-To: <20170526201351.GA21847@dhcp-216.srv.tuxera.com>
Hi Rkesh,
this looks reasonable, but we'll need to also adopt the non-PCI
driver to the new state machine. I can give this a spin.
At that point we probably want to move nvme_reset into common
code somehow.
next prev parent reply other threads:[~2017-05-28 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 20:13 [PATCH V3] nvme: fix multiple ctrl removal scheduling Rakesh Pandit
2017-05-26 20:13 ` Rakesh Pandit
2017-05-28 9:40 ` Christoph Hellwig [this message]
2017-05-28 9:40 ` Christoph Hellwig
2017-05-28 11:47 ` Rakesh Pandit
2017-05-28 11:47 ` Rakesh Pandit
2017-05-30 10:09 ` Sagi Grimberg
2017-05-30 10:09 ` Sagi Grimberg
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=20170528094043.GA14199@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.