All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Jarno Rajahalme <jarno@ovn.org>
Cc: kbuild-all@01.org, netdev@vger.kernel.org,
	netfilter-devel@vger.kernel.org, dev@openvswitch.org,
	jarno@ovn.org
Subject: Re: [PATCH net-next v3 8/8] openvswitch: Interface with NAT.
Date: Thu, 26 Nov 2015 10:39:16 +0800	[thread overview]
Message-ID: <201511261030.W7y6vR2E%fengguang.wu@intel.com> (raw)
In-Reply-To: <1448496501-109561-9-git-send-email-jarno@ovn.org>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

Hi Jarno,

[auto build test ERROR on net-next/master]

url:    https://github.com/0day-ci/linux/commits/Jarno-Rajahalme/openvswitch-NAT-support/20151126-081504
config: x86_64-randconfig-n0-11260924 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All errors (new ones prefixed by >>):

   net/built-in.o: In function `__ovs_ct_lookup':
>> conntrack.c:(.text+0x262f6a): undefined reference to `nf_nat_icmp_reply_translation'
>> conntrack.c:(.text+0x26321b): undefined reference to `nf_nat_icmpv6_reply_translation'

---
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: 26415 bytes --]

  reply	other threads:[~2015-11-26  2:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-26  0:08 [PATCH net-next v3 0/8] openvswitch: NAT support Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 2/8] netfilter: Factor out nf_ct_get_info() Jarno Rajahalme
2015-11-26  6:18   ` [ovs-dev] " Simon Horman
     [not found] ` <1448496501-109561-1-git-send-email-jarno-LZ6Gd1LRuIk@public.gmane.org>
2015-11-26  0:08   ` [PATCH net-next v3 1/8] netfilter: Remove IP_CT_NEW_REPLY definition Jarno Rajahalme
2015-11-26  5:41     ` [ovs-dev] " Simon Horman
     [not found]       ` <20151126054100.GB21626-IxS8c3vjKQDk1uMJSBkQmQ@public.gmane.org>
2015-11-30 18:16         ` Jarno Rajahalme
     [not found]           ` <391067B3-D60E-43BC-B669-2DD45924E5D8-LZ6Gd1LRuIk@public.gmane.org>
2015-12-01  2:46             ` Jarno Rajahalme
2015-11-26  0:08   ` [PATCH net-next v3 3/8] netfilter: Allow calling into nat helper without skb_dst Jarno Rajahalme
2015-12-01 20:51     ` [PATCH net-next v3 3/8] netfilter: Allow calling into nat helper without skb_dst.g Pablo Neira Ayuso
2015-12-04 23:45       ` [ovs-dev] " Pravin Shelar
2015-11-26  0:08   ` [PATCH net-next v3 4/8] openvswitch: Update the CT state key only after nf_conntrack_in() Jarno Rajahalme
2015-11-26  0:08   ` [PATCH net-next v3 5/8] openvswitch: Find existing conntrack entry after upcall Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 6/8] openvswitch: Handle NF_REPEAT in conntrack action Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 7/8] openvswitch: Delay conntrack helper call for new connections Jarno Rajahalme
2015-11-26  0:08 ` [PATCH net-next v3 8/8] openvswitch: Interface with NAT Jarno Rajahalme
2015-11-26  2:39   ` kbuild test robot [this message]
2015-11-26  4:19   ` kbuild test robot

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=201511261030.W7y6vR2E%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 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.