From: hch@infradead.org (Christoph Hellwig)
Subject: nvme-cli won't build
Date: Mon, 26 Sep 2016 15:15:44 -0700 [thread overview]
Message-ID: <20160926221544.GA6978@infradead.org> (raw)
In-Reply-To: <026701d21843$3f68bd70$be3a3850$@opengridcomputing.com>
On Mon, Sep 26, 2016@05:13:45PM -0500, Steve Wise wrote:
> Anybody know what's up here? I've got linux-4.8-rc8 kernel built/installed and
> the latest nvme-cli pulled, but nvme-cli fails to build.
Looks like your Linux headers are missing it. It should be fairly easy
to avoid the need for it, let me see if I can do that.
next prev parent reply other threads:[~2016-09-26 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 22:13 nvme-cli won't build Steve Wise
2016-09-26 22:15 ` Christoph Hellwig [this message]
2016-09-27 14:50 ` Christoph Hellwig
2016-09-27 14:54 ` Steve Wise
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=20160926221544.GA6978@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.