From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricard Wanderlof Subject: Re: linux-next: build failure after merge of the sound-asoc tree Date: Mon, 31 Aug 2015 09:04:22 +0200 Message-ID: References: <20150828115041.037554b4@canb.auug.org.au> <20150828154556.GO12027@sirena.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from bastet.se.axis.com ([195.60.68.11]:48176 "EHLO bastet.se.axis.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750922AbbHaHEZ (ORCPT ); Mon, 31 Aug 2015 03:04:25 -0400 In-Reply-To: <20150828154556.GO12027@sirena.org.uk> Sender: linux-next-owner@vger.kernel.org List-ID: To: Mark Brown Cc: Stephen Rothwell , Liam Girdwood , "linux-next@vger.kernel.org" , "linux-kernel@vger.kernel.org" On Fri, 28 Aug 2015, Mark Brown wrote: > On Fri, Aug 28, 2015 at 09:40:41AM +0200, Ricard Wanderlof wrote: > > On Fri, 28 Aug 2015, Stephen Rothwell wrote: >=20 > > In fact the exact same construct is used by a handful of other code= c=20 > > drivers which apparently don't fail. >=20 > > I'm suspecting something slightly more convoluted like a missing=20 > #include . >=20 > No, the issue is that you have used a different variable name when=20 > declaring the IDs and when referencing them in the module device tabl= e. Yeah, I realized that upon closer inspection.=20 What bugs me is that my ARM gcc didn't seem to flag this, whereas the=20 x86 gcc did upon subsequent testing. And yes, CONFIG_OF is set during m= y=20 build. /Ricard --=20 Ricard Wolf Wanderl=F6f ricardw(at)axis.com Axis Communications AB, Lund, Sweden www.axis.com Phone +46 46 272 2016 Fax +46 46 13 61 30