Hi,Chris

I had update my branch linux-mmc and test, there is no such err.
As u64 need the macro div_u64 in "include/linux/math64.h"

#ifndef div_u64
static inline u64 div_u64(u64 dividend, u32 divisor)
{
        u32 remainder;
        return div_u64_rem(dividend, divisor, &remainder);
}
#endif

As different vendor may redefine div_u64_rem or remove the func div_u64, it's 
possible.
In driver/mmc/ all func use data->timeout_ns without define div_u64 or not use 
div_u64 to divide will encounter this err. So I'm not sure which reason bring 
about this err.

Regards
Haijun.


> -----Original Message-----
> From: linux-mmc-ow...@vger.kernel.org [mailto:linux-mmc-
> ow...@vger.kernel.org] On Behalf Of Chris Ball
> Sent: Monday, November 26, 2012 7:51 AM
> To: kbuild test robot
> Cc: Zhang Haijun-B42677; linux-mmc@vger.kernel.org; Huang Changming-
> R66093
> Subject: Re: [mmc:mmc-next 45/63] of_iommu.c:(.text+0x114dbc): undefined
> reference to `__aeabi_uldivmod'
> 
> 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   <c...@laptop.org>   <http://printf.net/>
> One Laptop Per Child
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majord...@vger.kernel.org More majordomo info at
> http://vger.kernel.org/majordomo-info.html


--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to