From: Florian Westphal <fw@strlen.de>
To: kbuild test robot <lkp@intel.com>
Cc: Florian Westphal <fw@strlen.de>,
kbuild-all@01.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next] netfilter: conntrack: allow increasing bucket size via sysctl too
Date: Wed, 25 May 2016 12:04:50 +0200 [thread overview]
Message-ID: <20160525100450.GA22288@breakpoint.cc> (raw)
In-Reply-To: <201605251426.gLgNgu5U%fengguang.wu@intel.com>
kbuild test robot <lkp@intel.com> wrote:
> url: https://github.com/0day-ci/linux/commits/Florian-Westphal/netfilter-conntrack-allow-increasing-bucket-size-via-sysctl-too/20160516-014623
> base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next master
> config: x86_64-randconfig-n0-05251422 (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
> Note: the linux-review/Florian-Westphal/netfilter-conntrack-allow-increasing-bucket-size-via-sysctl-too/20160516-014623 HEAD 5f39f4af5e5d9cf4d678faa29015e6aa5b89513d builds fine.
> It only hurts bisectibility.
>
> All errors (new ones prefixed by >>):
>
> net/netfilter/nf_conntrack_standalone.c: In function 'nf_conntrack_standalone_init':
> >> net/netfilter/nf_conntrack_standalone.c:640:2: error: 'nf_conntrack_htable_size_user' undeclared (first use in this function)
> nf_conntrack_htable_size_user = nf_conntrack_htable_size;
> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> net/netfilter/nf_conntrack_standalone.c:640:2: note: each undeclared identifier is reported only once for each function it appears in
I'll send a v2 once -next is open again.
prev parent reply other threads:[~2016-05-25 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-15 17:45 [PATCH nf-next] netfilter: conntrack: allow increasing bucket size via sysctl too Florian Westphal
2016-05-25 6:56 ` kbuild test robot
2016-05-25 10:04 ` Florian Westphal [this message]
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=20160525100450.GA22288@breakpoint.cc \
--to=fw@strlen.de \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--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).