From: Lokesh Vutla <lokeshvutla@ti.com>
To: Venkatraman S <svenkatr@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>, peter.ujfalusi@ti.com
Subject: Re: Error when building modules for omap2plus_defconfig in mainline
Date: Thu, 11 Oct 2012 13:29:05 +0530 [thread overview]
Message-ID: <50767C49.8080304@ti.com> (raw)
In-Reply-To: <50766EEE.8000006@ti.com>
Hi Venkat,
On Thursday 11 October 2012 12:32 PM, Venkatraman S wrote:
> Daily build on Linus's tree is failing for the past 2-3 days
> make "modules" with omap2plus_defconfig..
>
> ERROR: "snd_hwparams_to_dma_slave_config"
> [sound/soc/omap/snd-soc-omap.ko] undefined!
> ERROR: "snd_dmaengine_pcm_pointer" [sound/soc/omap/snd-soc-omap.ko]
> undefined!
> ERROR: "snd_dmaengine_pcm_open" [sound/soc/omap/snd-soc-omap.ko] undefined!
> ERROR: "snd_dmaengine_pcm_close" [sound/soc/omap/snd-soc-omap.ko]
> undefined!
> ERROR: "snd_dmaengine_pcm_get_chan" [sound/soc/omap/snd-soc-omap.ko]
> undefined!
> ERROR: "snd_dmaengine_pcm_trigger" [sound/soc/omap/snd-soc-omap.ko]
> undefined!
> make[2]: *** [__modpost] Error 1
> make[1]: *** [modules] Error 2
> make: *** [sub-make] Error 2
>
> Just wanted to check if a fix is already on the way for -rc1 or someone
> is aware of it..
This is already fixed by Peter. Here is the patch
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-October/055902.html
Thanks
Lokesh
>
> Thanks,
> Venkat.
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-10-11 7:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 7:02 Error when building modules for omap2plus_defconfig in mainline Venkatraman S
2012-10-11 7:59 ` Lokesh Vutla [this message]
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=50767C49.8080304@ti.com \
--to=lokeshvutla@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=svenkatr@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.