From: Kalle Valo <kalle.valo@iki.fi>
To: linux-omap@vger.kernel.org
Subject: n800 build error in clock24xx.c: 'secure_32k_ck' undeclared
Date: Fri, 17 Apr 2009 23:44:16 +0300 [thread overview]
Message-ID: <873ac7ko2n.fsf@litku.valot.fi> (raw)
Hello,
I'm trying to compile n800 kernel with latest linux-omap tree. First I
got strange build error:
arch/arm/kernel/sys_oabi-compat.c: In function 'sys_oabi_epoll_wait':
arch/arm/kernel/sys_oabi-compat.c:289: error: implicit declaration of function 'kmalloc'
arch/arm/kernel/sys_oabi-compat.c:289: warning: assignment makes pointer from integer without a cast
arch/arm/kernel/sys_oabi-compat.c:302: error: implicit declaration of function 'kfree'
arch/arm/kernel/sys_oabi-compat.c: In function 'sys_oabi_semtimedop':
arch/arm/kernel/sys_oabi-compat.c:325: warning: assignment makes pointer from integer without a cast
Adding include <linux/slab.h> made it go away but then I got this:
In file included from arch/arm/mach-omap2/clock24xx.c:46:
arch/arm/mach-omap2/clock24xx.h:1801: error: 'secure_32k_ck' undeclared here (not in a function)
Any hints?
The latest commit I have is:
commit 8e58316ba38aa6ffd53e2ada59142ad40cf47744
Merge: 1232332 0932667
Author: Tony Lindgren <tony@atomide.com>
Date: Wed Apr 15 11:22:24 2009 -0700
Merge branch 'omap-pool'
--
Kalle Valo
next reply other threads:[~2009-04-17 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 20:44 Kalle Valo [this message]
2009-04-19 5:00 ` n800 build error in clock24xx.c: 'secure_32k_ck' undeclared green
2009-04-19 15:58 ` Kalle Valo
2009-04-20 1:23 ` green
2009-04-20 17:38 ` Tony Lindgren
2009-04-20 17:47 ` Paul Walmsley
2009-04-20 17:56 ` Paul Walmsley
2009-04-20 18:06 ` [APPLIED] n800 build error in clock24xx.c: 'secure_32k_ck' undeclared Tony Lindgren
2009-04-23 15:37 ` n800 build error in clock24xx.c: 'secure_32k_ck' undeclared Kalle Valo
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=873ac7ko2n.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=linux-omap@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