From: kbuild test robot <fengguang.wu@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org
Subject: [nf-next:for-net-next3 36/40] (.text.nf_saveroute+0x58): undefined reference to `nf_ip6_saveroute'
Date: Wed, 20 Dec 2017 12:05:26 +0800 [thread overview]
Message-ID: <201712201224.uKqTECip%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git for-net-next3
head: dfbb1c16489ca1b93e3f8aebc74d9229f1d87cc6
commit: e58c72119d0fa35020c144317509fe9494c441bd [36/40] netfilter: remove saveroute indirection in struct nf_afinfo
config: parisc-allmodconfig (attached as .config)
compiler: hppa-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout e58c72119d0fa35020c144317509fe9494c441bd
# save the attached .config to linux build tree
make.cross ARCH=parisc
All errors (new ones prefixed by >>):
net/netfilter/utils.o: In function `nf_checksum':
(.text.nf_checksum+0x78): undefined reference to `nf_ip6_checksum'
net/netfilter/utils.o: In function `nf_checksum_partial':
(.text.nf_checksum_partial+0x88): undefined reference to `nf_ip6_checksum_partial'
net/netfilter/utils.o: In function `nf_saveroute':
>> (.text.nf_saveroute+0x58): undefined reference to `nf_ip6_saveroute'
---
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: 51410 bytes --]
reply other threads:[~2017-12-20 4:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201712201224.uKqTECip%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=coreteam@netfilter.org \
--cc=kbuild-all@01.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).