From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter•org>,
NetFilter <netfilter-devel@vger•kernel.org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Liping Zhang <liping.zhang@spreadtrum•com>
Subject: linux-next: build failure after merge of the netfilter-next tree
Date: Thu, 18 Aug 2016 11:56:57 +1000 [thread overview]
Message-ID: <20160818115657.56eb079f@canb.auug.org.au> (raw)
Hi all,
After merging the netfilter-next tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
ERROR: "nf_conntrack_htable_size" [net/netfilter/nf_conntrack_netlink.ko] undefined!
ERROR: "nf_conntrack_htable_size" [net/ipv4/netfilter/nf_conntrack_ipv4.ko] undefined!
Caused by commit
adf0516845bc ("netfilter: remove ip_conntrack* sysctl compat code")
or maybe
92e47ba8839b ("netfilter: conntrack: simplify the code by using nf_conntrack_get_ht")
I have used the netfilter-next tree from next-20160817 for today.
--
Cheers,
Stephen Rothwell
next reply other threads:[~2016-08-18 1:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 1:56 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-18 1:50 linux-next: build failure after merge of the netfilter-next tree Stephen Rothwell
2018-10-15 23:41 Stephen Rothwell
2018-10-16 8:02 ` Pablo Neira Ayuso
2019-01-20 23:36 Stephen Rothwell
2019-02-13 5:54 Stephen Rothwell
2019-04-12 6:37 Stephen Rothwell
2019-04-12 8:15 ` Florian Westphal
2019-04-13 4:05 ` Stephen Rothwell
2019-04-12 16:36 ` Pablo Neira Ayuso
2019-06-20 13:47 Stephen Rothwell
2019-06-20 13:57 ` Pablo Neira Ayuso
2019-06-20 14:16 ` Stephen Rothwell
2019-07-08 3:39 Stephen Rothwell
2019-07-09 3:59 ` Stephen Rothwell
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=20160818115657.56eb079f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=liping.zhang@spreadtrum$(echo .)com \
--cc=netfilter-devel@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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