From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: trouble compiling dwalker's for-next tree
Date: Sat, 9 Jan 2010 09:51:06 +0100 [thread overview]
Message-ID: <20100109085106.GA23290@elf.ucw.cz> (raw)
Hi!
It is great to have all changes merged, but I ran into some trouble:
1) mmc.h was missing.
2) CC arch/arm/mach-msm/rpc_hsusb.o
arch/arm/mach-msm/rpc_hsusb.c: In function 'msm_chg_rpc_connect':
arch/arm/mach-msm/rpc_hsusb.c:156: error: implicit declaration of
function 'machine_is_msm7201a_surf'
arch/arm/mach-msm/rpc_hsusb.c:156: error: implicit declaration of
function 'machine_is_msm7x27_surf'
arch/arm/mach-msm/rpc_hsusb.c:157: error: implicit declaration of
function 'machine_is_qsd8x50_surf'
make[1]: *** [arch/arm/mach-msm/rpc_hsusb.o] Error 1
(I provided missing inlines)
3) CC arch/arm/mach-msm/acpuclock.o
arch/arm/mach-msm/acpuclock.c:31:35: error: linux/remote_spinlock.h:
No such file or directory
arch/arm/mach-msm/acpuclock.c:106: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'pll_lock'
(I'm currently stuck here).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next reply other threads:[~2010-01-09 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 8:51 Pavel Machek [this message]
2010-01-10 15:19 ` trouble compiling dwalker's for-next tree Daniel Walker
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=20100109085106.GA23290@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).