From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Wei, FangfangX" <fangfangx.wei@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
gowrishankar muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] FW: [dpdk-test-report] | ERROR | daily Intel builds (37/43)
Date: Wed, 15 Mar 2017 08:58:20 +0000 [thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E45123697821EE478@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <067B569323FEB248B5CB480E1954F4346EA0FC92@SHSMSX101.ccr.corp.intel.com>
> Hi all,
> There's one build error which was brought by commit
> "0fe9830b53452a6747cae9ff1a6bfc737b839a9d".
>
> commit 0fe9830b53452a6747cae9ff1a6bfc737b839a9d
> Author: Gowrishankar Muthukrishnan
> <gowrishankar.m@linux.vnet.ibm.com>
Hi Gowrishankar,
It seems we missed a vfio_iommu_spapr_tce_info structure in our conditional define for older kernels, so it breaks compile on those kernels.
Thanks,
Anatoly
prev parent reply other threads:[~2017-03-15 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <63cbe6$121995t@fmsmga002.fm.intel.com>
2017-03-15 8:06 ` Wei, FangfangX
2017-03-15 8:58 ` Burakov, Anatoly [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=C6ECDF3AB251BE4894318F4E45123697821EE478@IRSMSX109.ger.corp.intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=fangfangx.wei@intel.com \
--cc=gowrishankar.m@linux.vnet.ibm.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).