From: Chris Ball <cjb@laptop.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Haijun Zhang <Haijun.Zhang@freescale.com>,
linux-mmc@vger.kernel.org,
Jerry Huang <Chang-Ming.Huang@freescale.com>
Subject: Re: [mmc:mmc-next 45/63] of_iommu.c:(.text+0x114dbc): undefined reference to `__aeabi_uldivmod'
Date: Sun, 25 Nov 2012 18:51:02 -0500 [thread overview]
Message-ID: <87sj7x9r89.fsf@octavius.laptop.org> (raw)
In-Reply-To: <50b2a62c.slEE/d1mNq4kUCUf%fengguang.wu@intel.com> (kbuild test robot's message of "Mon, 26 Nov 2012 07:13:48 +0800")
Hi,
On Sun, Nov 25 2012, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git mmc-next
> head: b1dc46e6cd5f314f52a9864cc7ba1b7624b54bd7
> commit: d29254e21ddddee37b3c8525817398d96d6403f3 [45/63] mmc: core:
> Use u64 to calculate the timeout value to avoid overflow
> config: make ARCH=arm omap2plus_defconfig
>
> All error/warnings:
>
> drivers/built-in.o: In function `mmc_omap_start_request':
> of_iommu.c:(.text+0x114dbc): undefined reference to `__aeabi_uldivmod'
I've removed Haijun's three patches from mmc-next while they're reworked
to fix this. Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-11-25 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 23:13 [mmc:mmc-next 45/63] of_iommu.c:(.text+0x114dbc): undefined reference to `__aeabi_uldivmod' kbuild test robot
2012-11-25 23:51 ` Chris Ball [this message]
2012-11-26 4:11 ` Zhang Haijun-B42677
2012-11-26 10:02 ` Zhang Haijun-B42677
2012-12-14 2:52 ` Zhang Haijun-B42677
2013-01-15 2:03 ` Zhang Haijun-B42677
2012-11-26 5:54 ` Huang Changming-R66093
2012-11-26 6:02 ` Fengguang Wu
2012-11-26 6:12 ` Zhang Haijun-B42677
2012-11-26 6:21 ` Fengguang Wu
2012-11-26 7:23 ` Zhang Haijun-B42677
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=87sj7x9r89.fsf@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=Chang-Ming.Huang@freescale.com \
--cc=Haijun.Zhang@freescale.com \
--cc=fengguang.wu@intel.com \
--cc=linux-mmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.