From: kbuild test robot <lkp@intel.com>
To: Jarno Rajahalme <jarno@ovn.org>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
netdev@vger.kernel.org, dev@openvswitch.org, jarno@ovn.org
Subject: Re: [PATCH nf-next v8 8/8] openvswitch: Interface with NAT.
Date: Wed, 9 Mar 2016 16:04:05 +0800 [thread overview]
Message-ID: <201603091647.Hv6Rrs7K%fengguang.wu@intel.com> (raw)
In-Reply-To: <1457483084-13944-8-git-send-email-jarno@ovn.org>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Hi Jarno,
[auto build test ERROR on nf-next/master]
url: https://github.com/0day-ci/linux/commits/Jarno-Rajahalme/netfilter-Remove-IP_CT_NEW_REPLY-definition/20160309-083126
base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next master
config: i386-randconfig-x0-03091344 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
net/built-in.o: In function `__ovs_ct_lookup':
>> conntrack.c:(.text+0x227267): undefined reference to `nf_ct_nat_ext_add'
>> conntrack.c:(.text+0x227404): undefined reference to `nf_nat_icmp_reply_translation'
conntrack.c:(.text+0x2274ab): undefined reference to `nf_nat_icmpv6_reply_translation'
>> conntrack.c:(.text+0x227585): undefined reference to `nf_nat_setup_info'
>> conntrack.c:(.text+0x2275a1): undefined reference to `nf_nat_alloc_null_binding'
>> conntrack.c:(.text+0x2275d2): undefined reference to `nf_nat_packet'
---
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: 25339 bytes --]
next prev parent reply other threads:[~2016-03-09 8:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 0:24 [PATCH nf-next v8 1/8] netfilter: Remove IP_CT_NEW_REPLY definition Jarno Rajahalme
[not found] ` <1457483084-13944-1-git-send-email-jarno-LZ6Gd1LRuIk@public.gmane.org>
2016-03-09 0:24 ` [PATCH nf-next v8 2/8] netfilter: Allow calling into nat helper without skb_dst Jarno Rajahalme
2016-03-09 0:24 ` [PATCH nf-next v8 3/8] openvswitch: Add commentary to conntrack.c Jarno Rajahalme
2016-03-09 13:50 ` Sergei Shtylyov
[not found] ` <56E02A15.6030005-M4DtvfQ/ZS1MRgGoP+s0PdBPR1lH4CV8@public.gmane.org>
2016-03-09 23:14 ` Jarno Rajahalme
2016-03-09 0:24 ` [PATCH nf-next v8 4/8] openvswitch: Update the CT state key only after nf_conntrack_in() Jarno Rajahalme
2016-03-09 0:24 ` [PATCH nf-next v8 5/8] openvswitch: Find existing conntrack entry after upcall Jarno Rajahalme
2016-03-09 0:24 ` [PATCH nf-next v8 6/8] openvswitch: Handle NF_REPEAT in conntrack action Jarno Rajahalme
2016-03-09 0:24 ` [PATCH nf-next v8 7/8] openvswitch: Delay conntrack helper call for new connections Jarno Rajahalme
2016-03-09 0:24 ` [PATCH nf-next v8 8/8] openvswitch: Interface with NAT Jarno Rajahalme
2016-03-09 5:21 ` kbuild test robot
2016-03-09 5:34 ` kbuild test robot
2016-03-09 8:04 ` kbuild test robot [this message]
2016-03-09 23:11 ` Jarno Rajahalme
2016-03-10 9:16 ` [PATCH nf-next v8 1/8] netfilter: Remove IP_CT_NEW_REPLY definition Or Gerlitz
2016-03-10 18:44 ` Jarno Rajahalme
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=201603091647.Hv6Rrs7K%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=dev@openvswitch.org \
--cc=jarno@ovn.org \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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).