From: Felipe Contreras <felipe.contreras@gmail.com>
To: g3vbv@blueyonder.co.uk
Cc: LKML Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.32-rc5 omap build error
Date: Sun, 1 Nov 2009 13:53:29 +0200 [thread overview]
Message-ID: <94a0d4530911010353n38d0627ev69bf891005365e9@mail.gmail.com> (raw)
In-Reply-To: <4AE7BA65.6070502@blueyonder.co.uk>
On Wed, Oct 28, 2009 at 5:28 AM, Sid Boyce <g3vbv@blueyonder.co.uk> wrote:
> [root@localhost linux-omap-2.6]# ARCH=arm make
> CROSS_COMPILE=/opt/arm-2009q1/bin/arm-none-linux-gnueabi- uImage modules
> CHK include/linux/version.h
> make[1]: `include/asm-arm/mach-types.h' is up to date.
> CHK include/linux/utsrelease.h
> SYMLINK include/asm -> include/asm-arm
> CALL scripts/checksyscalls.sh
> CHK include/linux/compile.h
> CHK include/linux/version.h
> make[2]: `scripts/unifdef' is up to date.
> Kernel: arch/arm/boot/Image is ready
> Kernel: arch/arm/boot/zImage is ready
> UIMAGE arch/arm/boot/uImage
> Image Name: Linux-2.6.32-rc5-06331-g0bbf533-
> Created: Wed Oct 28 01:57:13 2009
> Image Type: ARM Linux Kernel Image (uncompressed)
> Data Size: 2236872 Bytes = 2184.45 kB = 2.13 MB
> Load Address: 0x80008000
> Entry Point: 0x80008000
> Image arch/arm/boot/uImage is ready
> Building modules, stage 2.
> MODPOST 355 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
Why don't you send this to the linux-omap mailing list?
--
Felipe Contreras
next prev parent reply other threads:[~2009-11-01 11:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 3:28 Sid Boyce
2009-11-01 11:53 ` Felipe Contreras [this message]
2009-11-01 16:11 ` 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=94a0d4530911010353n38d0627ev69bf891005365e9@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®