From: keith.busch@intel.com (Keith Busch)
Subject: "nvme-cli : wrong connection string for /dev/nvme-facrics (FC)"
Date: Mon, 4 Feb 2019 14:48:30 -0700 [thread overview]
Message-ID: <20190204214830.GE22199@localhost.localdomain> (raw)
In-Reply-To: <7b8e7f70-d520-2a64-ba5b-636dc033fe04@broadcom.com>
On Mon, Feb 04, 2019@01:41:04PM -0800, James Smart wrote:
> Eyal,
>
> Yes, that patch switched things up on FC and made it no longer match the fc
> transport.
> I just submitted a patch to correct it.
And patch is now applied, thanks for the fix.
prev parent reply other threads:[~2019-02-04 21:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 15:36 "nvme-cli : wrong connection string for /dev/nvme-facrics (FC)" Eyal BenDavid
2019-02-04 21:41 ` James Smart
2019-02-04 21:48 ` Keith Busch [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=20190204214830.GE22199@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