From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 8/8] nvme: properly handle partially initialized queues in nvme_create_io_queues
Date: Fri, 9 Oct 2015 08:15:06 +0200 [thread overview]
Message-ID: <20151009061506.GA28370@lst.de> (raw)
In-Reply-To: <56169138.90804@dev.mellanox.co.il>
On Thu, Oct 08, 2015@06:52:24PM +0300, Sagi Grimberg wrote:
> On 10/3/2015 4:39 PM, Christoph Hellwig wrote:
>> This avoids having to clean up later in a seemingly unrelated place.
>>
>> Signed-off-by: Christoph Hellwig <hch at lst.de>
>> Reviewed-by: Christoph Hellwig <hch at lst.de>
>
> I assume Keith reviewed this one correct? :)
He did reply with a reviewed-by tag to the previous posting of the series,
I think that qualifies.
next prev parent reply other threads:[~2015-10-09 6:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 13:39 nvme reset and probe updates V2 Christoph Hellwig
2015-10-03 13:39 ` [PATCH 1/8] NVMe: Reference count open namespaces Christoph Hellwig
2015-10-08 15:43 ` Sagi Grimberg
2015-10-08 15:47 ` Keith Busch
2015-10-03 13:39 ` [PATCH 2/8] NVMe: Namespace removal simplifications Christoph Hellwig
2015-10-08 15:47 ` Sagi Grimberg
2015-10-03 13:39 ` [PATCH 3/8] NVMe: Simplify device resume on io queue failure Christoph Hellwig
2015-10-03 13:39 ` [PATCH 4/8] nvme: delete dev from dev_list in nvme_reset Christoph Hellwig
2015-10-03 13:39 ` [PATCH 5/8] nvme: merge nvme_dev_reset into nvme_reset_failed_dev Christoph Hellwig
2015-10-03 13:39 ` [PATCH 6/8] nvme: factor reset code into a common helper Christoph Hellwig
2015-10-03 13:39 ` [PATCH 7/8] nvme: merge nvme_dev_start, nvme_dev_resume and nvme_async_probe Christoph Hellwig
2015-10-03 13:39 ` [PATCH 8/8] nvme: properly handle partially initialized queues in nvme_create_io_queues Christoph Hellwig
2015-10-08 15:52 ` Sagi Grimberg
2015-10-09 6:15 ` Christoph Hellwig [this message]
2015-10-09 14:20 ` Keith Busch
2015-10-09 14:39 ` Christoph Hellwig
2015-10-09 16:16 ` Jens Axboe
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=20151009061506.GA28370@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.