From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
bruce.richardson@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] dpdk-next-eventdev git pull request for RC1
Date: Wed, 5 Apr 2017 18:45:53 +0530 [thread overview]
Message-ID: <20170405131551.GA30228@jerin> (raw)
In-Reply-To: <b2f2a4b5-0379-04ba-4005-878e74569610@intel.com>
-----Original Message-----
> Date: Wed, 5 Apr 2017 12:46:09 +0100
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> To: Thomas Monjalon <thomas.monjalon@6wind.com>, Jerin Jacob
> <jerin.jacob@caviumnetworks.com>
> CC: bruce.richardson@intel.com, dev@dpdk.org
> Subject: Re: [dpdk-dev] dpdk-next-eventdev git pull request for RC1
> User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
> Thunderbird/45.8.0
>
> On 4/5/2017 9:04 AM, Thomas Monjalon wrote:
> > 2017-04-04 15:54, Jerin Jacob:
> >> On 17-04-04 09:13:38, Thomas Monjalon wrote:
> >>> Hi,
> >>>
> >>> When trying to pull the tree, the compilation failed at the third patch:
> >>> eventdev: implement the northbound APIs
> >>>
> >>> When building for x86_64:
> >>> In file included from lib/librte_eventdev/rte_eventdev.c:61:
> >>> lib/librte_eventdev/rte_eventdev.h:248:10: fatal error:
> >>> 'rte_mbuf.h' file not found
> >>>
> >>> Please, anyone to fix and check compilation on this tree?
> >>
> >> Fixed and rebased to
> >> dd18a2f0b vfio: fix secondary process start
> >
> > Pulled, thanks
> > and congratulations for the first merge of eventdev tree :)
>
> ICC produces following errors after merge:
How do we deal with ICC errors? I think, it shouldn't be community
responsibility.
>
> .../drivers/event/octeontx/ssovf_worker.c(212): error #592: variable
> "get_work0" is used before its value is set
> RTE_SET_USED(get_work0);
> ^
>
> .../drivers/event/octeontx/ssovf_worker.c(213): error #592: variable
> "get_work1" is used before its value is set
> RTE_SET_USED(get_work1);
> ^
>
> compilation aborted for .../drivers/event/octeontx/ssovf_worker.c (code 2)
> make[7]: *** [ssovf_worker.o] Error 2
>
> .../drivers/event/sw/sw_evdev_scheduler.c(379): error #300: const
> variable "dummy_rob" requires an initializer
> static const struct reorder_buffer_entry dummy_rob;
> ^
>
> compilation aborted for .../drivers/event/sw/sw_evdev_scheduler.c (code 2)
> make[7]: *** [sw_evdev_scheduler.o] Error 2
>
next prev parent reply other threads:[~2017-04-05 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 11:44 Jerin Jacob
2017-04-04 7:13 ` Thomas Monjalon
2017-04-04 7:34 ` Jerin Jacob
2017-04-04 10:24 ` Jerin Jacob
2017-04-05 8:04 ` Thomas Monjalon
2017-04-05 11:46 ` Ferruh Yigit
2017-04-05 13:15 ` Jerin Jacob [this message]
2017-04-05 14:18 ` Ferruh Yigit
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=20170405131551.GA30228@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=thomas.monjalon@6wind.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).