From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] nvme-core: Use nvme_wq to queue async events and fw activation
Date: Wed, 20 Sep 2017 19:55:05 +0200 [thread overview]
Message-ID: <20170920175505.GA18161@lst.de> (raw)
In-Reply-To: <1505905573-25371-1-git-send-email-sagi@grimberg.me>
Looks fine,
Reviewed-by: Christoph Hellwig <hch at lst.de>
prev parent reply other threads:[~2017-09-20 17:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 11:06 [PATCH 1/2] nvme-core: Use nvme_wq to queue async events and fw activation Sagi Grimberg
2017-09-20 11:06 ` [PATCH 2/2] nvme-rdma: give up reconnect if state change fails Sagi Grimberg
2017-09-20 11:27 ` Johannes Thumshirn
2017-09-20 11:29 ` Sagi Grimberg
2017-09-20 12:04 ` Johannes Thumshirn
2017-09-20 17:55 ` Christoph Hellwig
2017-09-20 11:29 ` [PATCH 1/2] nvme-core: Use nvme_wq to queue async events and fw activation Johannes Thumshirn
2017-09-20 17:55 ` 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=20170920175505.GA18161@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.