DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] KNI broken again
Date: Mon, 20 Mar 2017 10:37:49 +0000	[thread overview]
Message-ID: <b0c072cb-9609-78c7-3bea-cbdc14dd8d5e@intel.com> (raw)
In-Reply-To: <20170320102544.2rhin63fotpjazsp@localhost.localdomain>

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/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
> 

      reply	other threads:[~2017-03-20 10:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-20 10:25 Jerin Jacob
2017-03-20 10:37 ` Ferruh Yigit [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=b0c072cb-9609-78c7-3bea-cbdc14dd8d5e@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.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).