From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Timur Tabi <timur@freescale.com>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>
Subject: Re: asoc multi-component: CPU DAI name is wrong
Date: Sat, 24 Jul 2010 10:42:47 +0100 [thread overview]
Message-ID: <1279964567.3097.5.camel@odin> (raw)
In-Reply-To: <4C49E5C7.8020500@freescale.com>
On Fri, 2010-07-23 at 13:56 -0500, Timur Tabi wrote:
> Liam Girdwood wrote:
> > My mistake, I'd missed something in the forward port. I've fixed the DAI
> > naming problem and you should see your DAI use the correct name.
>
> Looks like you forgot something:
>
> CC sound/soc/soc-core.o
> sound/soc/soc-core.c: In function 'snd_soc_register_dai':
> sound/soc/soc-core.c:2872: error: 'struct snd_soc_dai' has no member named 'id'
> sound/soc/soc-core.c: In function 'snd_soc_register_dais':
> sound/soc/soc-core.c:2949: error: 'struct snd_soc_dai' has no member named 'id'
> sound/soc/soc-core.c: In function 'snd_soc_register_platform':
> sound/soc/soc-core.c:3004: error: 'struct snd_soc_platform' has no member
> named 'id'
> sound/soc/soc-core.c: In function 'snd_soc_register_codec':
> sound/soc/soc-core.c:3102: error: 'struct snd_soc_codec' has no member named
> 'id'
> make[2]: *** [sound/soc/soc-core.o] Error 1
> make[1]: *** [sound/soc] Error 2
> make: *** [sound] Error 2
>
Sorry, now fixed. Sound had somehow been disabled in my upstream .config
and hence would build kernels.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
next prev parent reply other threads:[~2010-07-24 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 21:57 asoc multi-component: CPU DAI name is wrong Timur Tabi
2010-07-23 18:16 ` Liam Girdwood
2010-07-23 18:56 ` Timur Tabi
2010-07-24 9:42 ` Liam Girdwood [this message]
2010-07-26 18:57 ` Timur Tabi
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=1279964567.3097.5.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=timur@freescale.com \
/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