From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Remaining kautobuild errors with mainline
Date: Tue, 9 Sep 2008 08:59:29 +0100 [thread overview]
Message-ID: <20080909075929.GC9104@flint.arm.linux.org.uk> (raw)
Tony,
As of last nights merge of the ARM tree, the only remaining build error
is:
arch/arm/mach-omap1/built-in.o: In function `sx1_mmc_init':
board-sx1-mmc.c:(.init.text+0xd64): undefined reference to `omap_set_mmc_info'
arch/arm/mach-omap1/built-in.o: In function `h2_mmc_init':
arch/arm/mach-omap1/board-h2-mmc.c:98: undefined reference to `omap_set_mmc_info'
This seems to be because of arch/arm/plat-omap/devices.c not being up to
date; it seems to pass a struct omap_mmc_conf to the OMAP MMC driver,
but the MMC driver expects a struct omap_mmc_platform_data instead.
Can I lift just the MMC changes for arch/arm/plat-omap/devices.c from
the OMAP tree to fix this, or is there something more required for this?
next reply other threads:[~2008-09-09 7:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 7:59 Russell King - ARM Linux [this message]
2008-09-09 9:33 ` Remaining kautobuild errors with mainline Russell King - ARM Linux
2008-09-09 15:22 ` Tony Lindgren
2008-09-11 10:30 ` Pandita, Vikram
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=20080909075929.GC9104@flint.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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