From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH v1] nvme: Log the ctrl device name instead of the undelying pci device name
Date: Thu, 28 Jan 2016 14:49:01 +0000 [thread overview]
Message-ID: <20160128144900.GA3863@localhost.localdomain> (raw)
In-Reply-To: <1453126453-17976-1-git-send-email-sagig@mellanox.com>
On Mon, Jan 18, 2016@04:14:13PM +0200, Sagi Grimberg wrote:
> Having the ctrl name "nvmeX" seems much more friendly than
> the underlying device name. Also, with other nvme transports
> such as the soon to come nvme-loop we don't have an underlying
> device so it doesn't makes sense to make up one.
>
> In order to help matching an instance name to a pci function,
> we add a info print in nvme_probe.
>
> Signed-off-by: Sagi Grimberg <sagig at mellanox.com>
Acked-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2016-01-28 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 14:14 [PATCH v1] nvme: Log the ctrl device name instead of the undelying pci device name Sagi Grimberg
2016-01-24 10:48 ` Sagi Grimberg
2016-01-28 14:49 ` Keith Busch [this message]
2016-02-10 10:14 ` Sagi Grimberg
2016-02-10 15:52 ` 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=20160128144900.GA3863@localhost.localdomain \
--to=keith.busch@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).