From: kbuild test robot <lkp@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: kbuild-all@01.org, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org, davem@davemloft.net,
eric.dumazet@gmail.com, brouer@redhat.com,
Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH net-next V2] tun: introduce tx skb ring
Date: Wed, 15 Jun 2016 18:34:35 +0800 [thread overview]
Message-ID: <201606151811.8zCGlqMg%fengguang.wu@intel.com> (raw)
In-Reply-To: <1465979897-4445-1-git-send-email-jasowang@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
Hi,
[auto build test ERROR on net-next/master]
url: https://github.com/0day-ci/linux/commits/Jason-Wang/tun-introduce-tx-skb-ring/20160615-164041
config: x86_64-randconfig-s2-06151732 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> drivers/net/tun.c:74:29: fatal error: linux/skb_array.h: No such file or directory
#include <linux/skb_array.h>
^
compilation terminated.
vim +74 drivers/net/tun.c
68 #include <net/net_namespace.h>
69 #include <net/netns/generic.h>
70 #include <net/rtnetlink.h>
71 #include <net/sock.h>
72 #include <linux/seq_file.h>
73 #include <linux/uio.h>
> 74 #include <linux/skb_array.h>
75
76 #include <asm/uaccess.h>
77
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 30315 bytes --]
next prev parent reply other threads:[~2016-06-15 10:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 8:38 [PATCH net-next V2] tun: introduce tx skb ring Jason Wang
2016-06-15 10:34 ` kbuild test robot
2016-06-15 10:34 ` kbuild test robot [this message]
2016-06-15 11:52 ` Jamal Hadi Salim
2016-06-15 11:55 ` Jamal Hadi Salim
2016-06-16 7:08 ` Jason Wang
2016-06-15 11:55 ` Jamal Hadi Salim
2016-06-15 11:52 ` Jamal Hadi Salim
2016-06-17 0:01 ` David Miller
2016-06-17 0:01 ` David Miller
2016-06-17 0:41 ` Michael S. Tsirkin
2016-06-17 0:41 ` Michael S. Tsirkin
2016-06-17 7:22 ` Jason Wang
2016-06-17 7:22 ` Jason Wang
2016-06-22 18:18 ` Michael S. Tsirkin
2016-06-22 18:18 ` Michael S. Tsirkin
2016-06-23 5:14 ` Jason Wang
2016-06-23 5:14 ` Jason Wang
2016-06-28 7:09 ` Michael S. Tsirkin
2016-06-28 7:09 ` Michael S. Tsirkin
2016-06-30 1:50 ` Jason Wang
2016-06-30 1:50 ` Jason Wang
2016-06-15 8:38 Jason Wang
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=201606151811.8zCGlqMg%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@01.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.