From: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>, Liam Girdwood <lrg@ti.com>
Cc: "Mohammed, Afzal" <afzal@ti.com>,
Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Balbi, Felipe" <balbi@ti.com>, "Hunter, Jon" <jon-hunter@ti.com>,
Omar Ramirez Luna <omar.luna@linaro.org>,
"Vutla, Lokesh" <lokeshvutla@ti.com>
Subject: linux-next ASOC build break ? (Was... Re: Help needed with remaining plat headers)
Date: Fri, 28 Sep 2012 12:37:06 +0530 [thread overview]
Message-ID: <CAMQu2gzPC62SWn+aVPpEc6vngF=m5fofPxwgECAtWURoSLDiCQ@mail.gmail.com> (raw)
+ Peter, Liam in case they haven't seen the issue yet.
On Fri, Sep 28, 2012 at 12:28 PM, Vutla, Lokesh <lokeshvutla@ti.com> wrote:
> Hi,
> I see a module build failure in linux-next tree.
> Any one else facing this issue or I am missing something.
> Using master branch on
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> Below is the log .
>
> $ make modules -j 10
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> LD [M] drivers/video/omap2/dss/omapdss.o
> Building modules, stage 2.
[..]
> MODPOST 45 modules
> 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[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
reply other threads:[~2012-09-28 7:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAMQu2gzPC62SWn+aVPpEc6vngF=m5fofPxwgECAtWURoSLDiCQ@mail.gmail.com' \
--to=santosh.shilimkar@ti.com \
--cc=afzal@ti.com \
--cc=balbi@ti.com \
--cc=jon-hunter@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=lokeshvutla@ti.com \
--cc=lrg@ti.com \
--cc=omar.luna@linaro.org \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).