From: kbuild test robot <lkp@intel.com>
To: Sainath Grandhi <sainath.grandhi@intel.com>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, davem@davemloft.net,
mahesh@bandewar.net, linux-kernel@vger.kernel.org,
Sainath Grandhi <sainath.grandhi@intel.com>
Subject: Re: [PATCHv1 6/7] TAP: tap as an independent module
Date: Sat, 7 Jan 2017 20:32:17 +0800 [thread overview]
Message-ID: <201701072005.m9hgZCTp%fengguang.wu@intel.com> (raw)
In-Reply-To: <1483742009-19184-7-git-send-email-sainath.grandhi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
Hi Sainath,
[auto build test ERROR on net/master]
[also build test ERROR on v4.10-rc2 next-20170106]
[cannot apply to net-next/master]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Sainath-Grandhi/Refactor-macvtap-to-re-use-tap-functionality-by-other-virtual-intefaces/20170107-165707
config: x86_64-allyesdebian (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
drivers/built-in.o: In function `macvtap_dellink':
>> macvtap.c:(.text+0x7d3255): undefined reference to `tap_del_queues'
drivers/built-in.o: In function `macvtap_exit':
>> macvtap.c:(.text+0x7d32e2): undefined reference to `tap_destroy_cdev'
drivers/built-in.o: In function `macvtap_init':
>> macvtap.c:(.text+0x7d3308): undefined reference to `tap_create_cdev'
drivers/built-in.o: In function `macvtap_newlink':
>> macvtap.c:(.text+0x7d33df): undefined reference to `tap_handle_frame'
drivers/built-in.o: In function `macvtap_device_event':
>> macvtap.c:(.text+0x7d34b5): undefined reference to `tap_get_minor'
>> macvtap.c:(.text+0x7d34fe): undefined reference to `tap_free_minor'
macvtap.c:(.text+0x7d3586): undefined reference to `tap_free_minor'
>> macvtap.c:(.text+0x7d3594): undefined reference to `tap_queue_resize'
drivers/built-in.o: In function `vhost_net_ioctl':
net.c:(.text+0x11835a3): undefined reference to `tap_get_socket'
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 38068 bytes --]
next prev parent reply other threads:[~2017-01-07 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 22:33 [PATCHv1 0/7] Refactor macvtap to re-use tap functionality by other virtual intefaces Sainath Grandhi
2017-01-06 22:33 ` [PATCHv1 1/7] TAP: Refactoring macvtap.c Sainath Grandhi
2017-01-06 23:12 ` Andy Shevchenko
2017-01-06 22:33 ` [PATCHv1 2/7] TAP: Renaming tap related APIs, data structures, macros Sainath Grandhi
2017-01-07 10:44 ` kbuild test robot
2017-01-07 12:00 ` kbuild test robot
2017-01-06 22:33 ` [PATCHv1 3/7] TAP: Tap character device creation/destroy API Sainath Grandhi
2017-01-06 22:33 ` [PATCHv1 4/7] TAP: Abstract type of virtual interface from tap implementation Sainath Grandhi
2017-01-06 22:33 ` [PATCHv1 5/7] TAP: Extending tap device create/destroy APIs Sainath Grandhi
2017-01-06 23:15 ` Eric Dumazet
2017-01-17 23:07 ` Grandhi, Sainath
2017-01-06 23:20 ` Andy Shevchenko
2017-01-17 23:51 ` Grandhi, Sainath
2017-01-06 22:33 ` [PATCHv1 6/7] TAP: tap as an independent module Sainath Grandhi
2017-01-07 10:46 ` kbuild test robot
2017-01-07 12:32 ` kbuild test robot [this message]
2017-01-06 22:33 ` [PATCHv1 7/7] IPVTAP: IP-VLAN based tap driver Sainath Grandhi
2017-01-06 23:14 ` Eric Dumazet
2017-01-17 23:06 ` Grandhi, Sainath
2017-01-06 23:46 ` Mahesh Bandewar (महेश बंडेवार)
2017-01-17 23:49 ` Grandhi, Sainath
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=201701072005.m9hgZCTp%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh@bandewar.net \
--cc=netdev@vger.kernel.org \
--cc=sainath.grandhi@intel.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).