public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Pablo Neira Ayuso <pablo@netfilter•org>,
	NetFilter <netfilter-devel@vger•kernel.org>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Florian Westphal <fw@strlen•de>
Subject: linux-next: build failure after merge of the netfilter tree
Date: Mon, 15 Apr 2019 17:57:30 +1000	[thread overview]
Message-ID: <20190415175657.7824ebc6@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 517 bytes --]

Hi all,

After merging the netfilter-next tree, today's linux-next build (powerpc
allyesconfig) failed like this:

ld: net/netfilter/nf_conntrack_netlink.o: in function `__crc_nf_ct_get_id':
(.rodata+0x0): multiple definition of `__crc_nf_ct_get_id'; net/netfilter/nf_conntrack_core.o:(.rodata+0x20): first defined here

Caused by commit

  a5dc1fb1928a ("netfilter: ctnetlink: don't use conntrack/expect object addresses as id")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2019-04-15  7:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15  7:57 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-04-16 23:28 linux-next: build failure after merge of the netfilter tree Stephen Rothwell
2018-04-17  0:51 ` Cong Wang
2018-04-17  9:00   ` Pablo Neira Ayuso
2017-05-17  3:45 Stephen Rothwell
2017-05-17  5:02 ` Willem de Bruijn
2017-05-17 15:29   ` Willem de Bruijn
2017-05-17 23:10     ` 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=20190415175657.7824ebc6@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=fw@strlen$(echo .)de \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --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