From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wei, FangfangX" <fangfangx.wei@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: DPDK_SW_ENG <dpdk_sw_eng@intel.com>,
Alejandro Lucero <alejandro.lucero@netronome.com>
Subject: Re: [dpdk-dev] FW: [dpdk-test-report] | ERROR | daily Intel builds (33/55)
Date: Mon, 3 Apr 2017 17:53:23 +0100 [thread overview]
Message-ID: <7b43f0e5-e1ef-5e67-d645-0b3ccc5d6ee4@intel.com> (raw)
In-Reply-To: <067B569323FEB248B5CB480E1954F4346EA2D760@SHSMSX101.ccr.corp.intel.com>
On 4/1/2017 5:10 AM, Wei, FangfangX wrote:
> Hi all,
>
> There's one new build error:
> LD DPDK/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c: In function ‘igbuio_pci_probe’:
> DPDK/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:434:2: error: implicit declaration of function ‘dma_zalloc_coherent’
> cc1: warnings being treated as errors
> DPDK/x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:434:11: error: assignment makes pointer from integer without a cast
>
> It occurred by following commit:
> commit d287e4d41be0647aad5f341179f844cf304e0ea5
> Author: Alejandro Lucero <alejandro.lucero@netronome.com>
> Date: Wed Jan 18 12:27:55 2017 +0000
>
> igb_uio: map dummy DMA forcing IOMMU domain attachment
>
> Detail OSes and configuration please refer to Failure #1 and #2.
Sent following patch for the issue:
http://dpdk.org/dev/patchwork/patch/23166/
>
> Best Regards
> Fangfang Wei
prev parent reply other threads:[~2017-04-03 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15e752$p1j7f7@FMSMGA003.fm.intel.com>
2017-04-01 4:10 ` Wei, FangfangX
2017-04-03 16:53 ` Ferruh Yigit [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=7b43f0e5-e1ef-5e67-d645-0b3ccc5d6ee4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=dpdk_sw_eng@intel.com \
--cc=fangfangx.wei@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).