From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johan Hedberg Subject: Re: linux-next: build failure after merge of the bluetooth tree Date: Tue, 28 Oct 2014 15:49:33 +0100 Message-ID: <20141028144933.GA22555@t440s> References: <20141027131956.68b62e5e@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-lb0-f182.google.com ([209.85.217.182]:39683 "EHLO mail-lb0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750857AbaJ1Otq (ORCPT ); Tue, 28 Oct 2014 10:49:46 -0400 Received: by mail-lb0-f182.google.com with SMTP id f15so791467lbj.41 for ; Tue, 28 Oct 2014 07:49:45 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20141027131956.68b62e5e@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Gustavo Padovan , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, marcel@holtmann.org Hi Stephen, On Mon, Oct 27, 2014, Stephen Rothwell wrote: > After merging the bluetooth tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > net/bluetooth/smp.o: In function `test_smp': > smp.c:(.init.text+0x0): multiple definition of `init_module' > net/bluetooth/af_bluetooth.o:af_bluetooth.c:(.init.text+0x0): first defined here > > Probably caused by commit 4cd3362da899 ("Bluetooth: Add skeleton for > SMP self-tests"). > > I have used the bluetooth tree from next-20141023 for today. We've applied a revert patch for the SMP self-tests to the bluetooth-next tree until we figure out how to fix this properly. Johan