From: green <greenfreedom10@gmail.com>
To: linux-omap@vger.kernel.org
Subject: Re: n800 build error in clock24xx.c: 'secure_32k_ck' undeclared
Date: Sat, 18 Apr 2009 23:00:20 -0600 [thread overview]
Message-ID: <20090419050020.GC1736@swansys> (raw)
In-Reply-To: <873ac7ko2n.fsf@litku.valot.fi>
[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]
Kalle Valo wrote at 2009-04-17 14:44 -0600:
> I'm trying to compile n800 kernel with latest linux-omap tree. First I
> got strange build error:
Here too, on n810.
> 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
I see nearly the same:
arch/arm/kernel/sys_oabi-compat.c: In function ‘sys_oabi_epoll_wait’:
arch/arm/kernel/sys_oabi-compat.c:288: error: implicit declaration of function ‘kmalloc’
arch/arm/kernel/sys_oabi-compat.c:288: error: ‘GFP_KERNEL’ undeclared (first use in this function)
arch/arm/kernel/sys_oabi-compat.c:288: error: (Each undeclared identifier is reported only once
arch/arm/kernel/sys_oabi-compat.c:288: error: for each function it appears in.)
arch/arm/kernel/sys_oabi-compat.c:288: warning: assignment makes pointer from integer without a cast
arch/arm/kernel/sys_oabi-compat.c:301: 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:324: error: ‘GFP_KERNEL’ undeclared (first use in this function)
arch/arm/kernel/sys_oabi-compat.c:324: warning: assignment makes pointer from integer without a cast
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-04-19 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 20:44 n800 build error in clock24xx.c: 'secure_32k_ck' undeclared Kalle Valo
2009-04-19 5:00 ` green [this message]
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=20090419050020.GC1736@swansys \
--to=greenfreedom10@gmail.com \
--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