From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Compile ERROR: ‘pci_device_list’ undeclared
Date: Fri, 28 Apr 2017 16:31:20 +0000 [thread overview]
Message-ID: <1493397078.6290.30.camel@intel.com> (raw)
In-Reply-To: 25be06b4.7c75.15bb35f3e13.Coremail.dlworld0@163.com
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On Fri, 2017-04-28 at 15:03 +0800, 邓林文 wrote:
>
> Hi all, there's a compile error when I tried to test the latest SPDK. Is that
> a code bug or a misconfigure in my environment?
>
We merged a patch this morning that fixes the issue, but in general stick to the
latest released DPDK instead of tracking master. The DPDK team can potentially
change the API on each new commit on master, so we can't guarantee that it will
always be working. We'll make sure that SPDK works with any released version of
DPDK though.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]
next reply other threads:[~2017-04-28 16:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:31 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-28 16:14 [SPDK] Compile ERROR: ‘pci_device_list’ undeclared Luse, Paul E
2017-04-28 16:11 Harris, James R
2017-04-28 15:30 Luse, Paul E
2017-04-28 7:03
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=1493397078.6290.30.camel@intel.com \
--to=spdk@lists.01.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.