From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: dev@dpdk.org
Subject: [dpdk-dev] KNI broken again
Date: Mon, 20 Mar 2017 15:55:56 +0530 [thread overview]
Message-ID: <20170320102544.2rhin63fotpjazsp@localhost.localdomain> (raw)
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 ‘kni_net_process_request’:
/home/jerin/dpdk-next-net/build/build/lib/librte_eal/linuxapp/kni/kni_net.c:124:6:
error: implicit declaration of function ‘signal_pending’
[-Werror=implicit-function-declaration]
if (signal_pending(current) || ret_val <= 0) {
^
cc1: all warnings being treated as errors
/home/jerin/linux/scripts/Makefile.build:294: recipe for target
'/home/jerin/dpdk-next-net/build/build/lib/librte_eal/linuxapp/kni/kni_net.o' failed
➜ [dpdk-next-net] $ uname -a
Linux localhost.localdomain 4.11.0-rc3 #8 SMP Mon Mar 20 09:52:49 UTC 2017 aarch64 aarch64 aarch64 GNU/Linux
next reply other threads:[~2017-03-20 10:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 10:25 Jerin Jacob [this message]
2017-03-20 10:37 ` 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=20170320102544.2rhin63fotpjazsp@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--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).