From: Laura Garcia <nevola@gmail.com>
To: kbuild test robot <lkp@intel.com>
Cc: kbuild-all@01.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH v3] netfilter: nft_numgen: add number generator expression
Date: Wed, 17 Aug 2016 15:59:53 +0200 [thread overview]
Message-ID: <20160817135951.GA21214@sonyv> (raw)
In-Reply-To: <201608142357.TpQNQHIT%fengguang.wu@intel.com>
On Mon, Aug 15, 2016 at 12:03:19AM +0800, kbuild test robot wrote:
> Hi Laura,
>
> [auto build test ERROR on nf-next/master]
> [also build test ERROR on v4.8-rc1 next-20160812]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>
> url: https://github.com/0day-ci/linux/commits/Laura-Garcia-Liebana/netfilter-nft_numgen-add-number-generator-expression/20160814-185132
> base: https://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf-next.git master
> config: i386-allyesconfig (attached as .config)
> compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> # save the attached .config to linux build tree
> make ARCH=i386
>
> All errors (new ones prefixed by >>):
>
> >> net/netfilter/nft_numgen.o:(.discard+0x0): multiple definition of `__pcpu_unique_nft_prandom_state'
> net/netfilter/nft_meta.o:(.discard+0x0): first defined here
>
> ---
> 0-DAY kernel test infrastructure Open Source Technology Center
> https://lists.01.org/pipermail/kbuild-all Intel Corporation
Hi, I've been compiling with several options like:
CONFIG_NFT_META=m
CONFIG_NFT_NUMGEN=m
and
CONFIG_NFT_META=y
CONFIG_NFT_NUMGEN=y
but I was unable to reproduce it.
Anyway, I'll rename the identifier in a new patch.
Thanks.
prev parent reply other threads:[~2016-08-17 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 22:39 [PATCH v3] netfilter: nft_numgen: add number generator expression Laura Garcia Liebana
2016-08-14 16:03 ` kbuild test robot
2016-08-17 13:59 ` Laura Garcia [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=20160817135951.GA21214@sonyv \
--to=nevola@gmail.com \
--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).