From: kbuild test robot <lkp@intel.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: kbuild-all@01.org, netdev@vger.kernel.org, wenxu <wenxu@ucloud.cn>
Subject: [net-next:master 91/276] ERROR: "nf_ct_frag6_gather" [net/ipv6/ipv6.ko] undefined!
Date: Wed, 19 Jun 2019 13:12:59 +0800 [thread overview]
Message-ID: <201906191358.7iubzrgh%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 846 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git master
head: 39f5886032380e49119786b23274b38e9b3aa99c
commit: c9bb6165a16e6d5498981a6c777b94a78e74462b [91/276] netfilter: nf_conntrack_bridge: fix CONFIG_IPV6=y
config: i386-randconfig-n027-201924 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
git checkout c9bb6165a16e6d5498981a6c777b94a78e74462b
# save the attached .config to linux build tree
make ARCH=i386
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> ERROR: "nf_ct_frag6_gather" [net/ipv6/ipv6.ko] undefined!
---
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: 33110 bytes --]
reply other threads:[~2019-06-19 5:13 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=201906191358.7iubzrgh%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=wenxu@ucloud.cn \
/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