[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad2ff849-ea08-a384-b809-df2404116591@infradead.org>
Date: Wed, 11 Oct 2017 09:19:59 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Vinod Koul <vinod.koul@...el.com>
Cc: Mark Brown <broonie@...nel.org>,
Linux-Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Pierre-Yves Mordret <pierre-yves.mordret@...com>,
M'boumba Cedric Madianga <cedric.madianga@...il.com>,
"dmaengine@...r.kernel.org" <dmaengine@...r.kernel.org>
Subject: Re: linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c)
On 10/11/17 05:55, Vinod Koul wrote:
> On Tue, Oct 10, 2017 at 09:27:18AM -0700, Randy Dunlap wrote:
>> On 10/09/17 14:21, Mark Brown wrote:
>>> For my birthday I've gone and got myself a linux-next tree:
>
> Nice thing you chose to do for the day :D
>
>>>
>>> Changes since 20170929:
>>>
>>
>> on i386:
>>
>> drivers/dma/stm32-mdma.o: In function `stm32_mdma_prep_dma_memcpy':
>> stm32-mdma.c:(.text+0x1174): undefined reference to `__umoddi3'
>> stm32-mdma.c:(.text+0x1208): undefined reference to `__umoddi3'
>> stm32-mdma.c:(.text+0x134c): undefined reference to `__umoddi3'
>> stm32-mdma.c:(.text+0x141d): undefined reference to `__umoddi3'
>
> The driver uses DIV_ROUND_UP but this should have worked, let me check more.
> Was generic i386 defconfig used or some other config
Maybe look at the uses of '%' (modulus, as in __umoddi3).
--
~Randy
Powered by blists - more mailing lists