Re: [dpdk-dev] KNI broken again

2017-03-20 Thread Ferruh Yigit
On 3/20/2017 10:25 AM, Jerin Jacob wrote: > Found KNI broken in v4.11-rc3 Thanks for reporting, I confirm it, and will take care of it. Thanks, ferruh > > log: > > CC [M] > /home/jerin/dpdk-next-net/build/build/lib/librte_eal/linuxapp/kni/kni_misc.o > CC [M] > /home/jerin/dpdk-next-net/b

[dpdk-dev] KNI broken again

2017-03-20 Thread Jerin Jacob
Found KNI broken in v4.11-rc3 log: CC [M] /home/jerin/dpdk-next-net/build/build/lib/librte_eal/linuxapp/kni/kni_misc.o CC [M] /home/jerin/dpdk-next-net/build/build/lib/librte_eal/linuxapp/kni/kni_net.o /home/jerin/dpdk-next-net/build/build/lib/librte_eal/linuxapp/kni/kni_net.c: In function

Re: [dpdk-dev] KNI broken again with 4.9 kernel

2016-12-15 Thread Jay Rolette
On Thu, Dec 15, 2016 at 6:01 AM, Mcnamara, John wrote: > > > -Original Message- > > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Stephen Hemminger > > Sent: Wednesday, December 14, 2016 11:41 PM > > To: dev@dpdk.org > > Subject: [dpdk-dev]

Re: [dpdk-dev] KNI broken again with 4.9 kernel

2016-12-15 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Stephen Hemminger > Sent: Wednesday, December 14, 2016 11:41 PM > To: dev@dpdk.org > Subject: [dpdk-dev] KNI broken again with 4.9 kernel > > /build/lib/librte_eal/linuxapp/kni/igb_

Re: [dpdk-dev] KNI broken again with 4.9 kernel

2016-12-15 Thread Ferruh Yigit
Hi Stephen, I can't reproduce the error, I think it is not broken, that issue should be already fixed with commit [1]. On 12/14/2016 11:40 PM, Stephen Hemminger wrote: > /build/lib/librte_eal/linuxapp/kni/igb_main.c:2317:21: error: initialization > from incompatible pointer type [-Werror=incom

[dpdk-dev] KNI broken again with 4.9 kernel

2016-12-14 Thread Stephen Hemminger
/build/lib/librte_eal/linuxapp/kni/igb_main.c:2317:21: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .ndo_set_vf_vlan = igb_ndo_set_vf_vlan, ^~~ I am sure Ferruh Yigit will fix it. Which raises a couple of questio