From: swise@opengridcomputing.com (Steve Wise)
Subject: Windows NVMeoF client - debug assistance requested
Date: Tue, 21 Jun 2016 08:56:23 -0500 [thread overview]
Message-ID: <005401d1cbc4$b263ab80$172b0280$@opengridcomputing.com> (raw)
In-Reply-To: <3286b6ca966947ff8aca316b5ab56435@bowex36e.micron.com>
> I haven't updated my code since 6/8 and I'm using the nvmf-all.2 branch.
>
I had problems with nvmf-all.2 on linux. Perhaps you should try nvmf-all.3?
steve.
next prev parent reply other threads:[~2016-06-21 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 1:50 Windows NVMeoF client - debug assistance requested Robert Randall (rrandall)
2016-06-21 13:56 ` Steve Wise [this message]
2016-06-21 14:16 ` Robert Randall (rrandall)
2016-06-21 14:22 ` Steve Wise
2016-06-21 14:19 ` Sagi Grimberg
2016-06-21 14:55 ` Robert Randall
2016-06-21 15:20 ` Robert Randall
2016-06-21 16:02 ` Christoph Hellwig
2016-06-21 16:02 ` Robert Randall
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='005401d1cbc4$b263ab80$172b0280$@opengridcomputing.com' \
--to=swise@opengridcomputing.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 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.