From: Tony Lindgren <tony@atomide.com>
To: Sid Boyce <sboyce@blueyonder.co.uk>
Cc: linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [GIT PULL] omap build fixes
Date: Thu, 17 Dec 2009 09:26:01 -0800 [thread overview]
Message-ID: <20091217172600.GY4575@atomide.com> (raw)
In-Reply-To: <4B2A1635.1080505@blueyonder.co.uk>
* Sid Boyce <sboyce@blueyonder.co.uk> [091217 03:29]:
<snip>
> uImage built, so EHCI build problem definitely fixed, just one error
> I've previously encountered when building modules.
> slipstream:/home/lancelot/ftp/dec09/OMAP/omap-fixes-for-linus # ARCH=arm
> make -j 4 CROSS_COMPILE=/opt/arm-2009q3/bin/arm-none-eabi- modules
> scripts/kconfig/conf -s arch/arm/Kconfig
> CHK include/linux/version.h
> SYMLINK include/asm -> include/asm-arm
> make[1]: `include/asm-arm/mach-types.h' is up to date.
> CHK include/linux/utsrelease.h
> CALL scripts/checksyscalls.sh
> <stdin>:1523: warning: #warning syscall recvmmsg not implemented
> Building modules, stage 2.
> MODPOST 99 modules
> ERROR: "omap_ctrl_writel" [sound/soc/omap/snd-soc-omap-mcbsp.ko] undefined!
> ERROR: "omap_ctrl_readl" [sound/soc/omap/snd-soc-omap-mcbsp.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
Hmm. I'm not seeing this in any of the defconfigs, so I guess this
happens with ASoC complied as a module.
But instead of exporting omap_ctrl_read/write, we need to get rid of
omap_ctrl_read/write stuff in the drivers.
It seems that omap_mcbsp_dai_set_clks_src() should be implemented in
the clock framework instead.
Regards,
Tony
next prev parent reply other threads:[~2009-12-17 17:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 22:35 [GIT PULL] omap build fixes Tony Lindgren
2009-12-16 22:35 ` Tony Lindgren
2009-12-17 11:29 ` Sid Boyce
2009-12-17 17:26 ` Tony Lindgren [this message]
2009-12-17 22:16 ` Sid Boyce
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=20091217172600.GY4575@atomide.com \
--to=tony@atomide.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=sboyce@blueyonder.co.uk \
/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.