From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] KNI is broken with Linux 4.0
Date: Tue, 28 Apr 2015 09:48:35 -0700 [thread overview]
Message-ID: <20150428094835.407ccba9@urahara> (raw)
KNI won't build anymore. Since I don't use it not my problem.
CC [M] /var/src/dpdk/build/build/lib/librte_eal/linuxapp/kni/igb_main.o
/var/src/dpdk/build/build/lib/librte_eal/linuxapp/kni/igb_main.c:2321:2: error: initialization from incompatible pointer type [-Werror]
.ndo_bridge_setlink = igb_ndo_bridge_setlink,
^
/var/src/dpdk/build/build/lib/librte_eal/linuxapp/kni/igb_main.c:2321:2: error: (near initialization for ‘igb_netdev_ops.ndo_bridge_setlink’) [-Werror]
/var/src/dpdk/build/build/lib/librte_eal/linuxapp/kni/igb_main.c: In function ‘igb_xmit_frame_ring’:
/var/src/dpdk/build/build/lib/librte_eal/linuxapp/kni/igb_main.c:5482:2: error: implicit declaration of function ‘vlan_tx_tag_present’ [-Werror=implicit-function-declaration]
if (vlan_tx_tag_present(skb)) {
^
/var/src/dpdk/build/build/lib/librte_eal/linuxapp/kni/igb_main.c:5484:3: error: implicit declaration of function ‘vlan_tx_tag_get’ [-Werror=implicit-function-declaration]
tx_flags |= (vlan_tx_tag_get(skb) << IGB_TX_FLAGS_VLAN_SHIFT);
^
cc1: all warnings being treated as errors
Ps: this and all the other kernel drivers really need to be upstream
to avoid these kind of issues in the future.
reply other threads:[~2015-04-28 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20150428094835.407ccba9@urahara \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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 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).