Re: linux-next: build failure after merge of the sound-asoc tree
From: Stephen Rothwell
Date: Mon Aug 31 2015 - 03:48:50 EST
Hi Ricard,
On Mon, 31 Aug 2015 09:04:22 +0200 Ricard Wanderlof <ricard.wanderlof@xxxxxxxx> wrote:
>
> 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:
> >
> > > In fact the exact same construct is used by a handful of other codec
> > > drivers which apparently don't fail.
> >
> > > I'm suspecting something slightly more convoluted like a missing
> > #include .
> >
> > No, the issue is that you have used a different variable name when
> > declaring the IDs and when referencing them in the module device table.
>
> Yeah, I realized that upon closer inspection.
>
> What bugs me is that my ARM gcc didn't seem to flag this, whereas the
> x86 gcc did upon subsequent testing. And yes, CONFIG_OF is set during my
> build.
Do you have CONFIG_MODULE set in your build? (just guessing)
--
Cheers,
Stephen Rothwell sfr@xxxxxxxxxxxxxxxx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/