From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvme: Move nvme_freeze/unfreeze_queues to nvme core
Date: Mon, 14 Dec 2015 02:15:47 -0800 [thread overview]
Message-ID: <20151214101547.GA5783@infradead.org> (raw)
In-Reply-To: <1450024038-1694-1-git-send-email-sagig@mellanox.com>
On Sun, Dec 13, 2015@06:27:18PM +0200, Sagi Grimberg wrote:
> Nothing pci specific about them and We'll need them exported
> in other transports too.
Note that except for the loop over the namespaces there isn't anything
nvme specific either. I'm fine with the patch for now, but in the
long run it might make sense to move most of it to the block layer.
Reviewed-by: Christoph Hellwig <hch at lst.de>
prev parent reply other threads:[~2015-12-14 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-13 16:27 [PATCH] nvme: Move nvme_freeze/unfreeze_queues to nvme core Sagi Grimberg
2015-12-14 10:15 ` 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=20151214101547.GA5783@infradead.org \
--to=hch@infradead.org \
/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.