From: Vinod Koul <vinod.koul@intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Mark Brown <broonie@kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pierre-Yves Mordret <pierre-yves.mordret@st.com>,
M'boumba Cedric Madianga <cedric.madianga@gmail.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: Re: linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c)
Date: Wed, 11 Oct 2017 18:25:28 +0530 [thread overview]
Message-ID: <20171011125528.GI30097@localhost> (raw)
In-Reply-To: <a86da771-5abc-acc9-cc2e-c31984fba659@infradead.org>
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
--
~Vinod
next prev parent reply other threads:[~2017-10-11 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 21:21 linux-next: Tree for Oct 9th Mark Brown
2017-10-10 16:27 ` linux-next: Tree for Oct 9th (drivers/dma/stm32-mdma.c) Randy Dunlap
2017-10-11 12:55 ` Vinod Koul [this message]
2017-10-11 16:19 ` Randy Dunlap
2017-10-10 17:33 ` linux-next: Tree for Oct 9th (of: unittest: testcases) Randy Dunlap
[not found] ` <7524d1e5-137c-cb78-c24f-6a9701e46701-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2017-10-10 18:26 ` Rob Herring
2017-10-10 18:34 ` Randy Dunlap
2017-10-11 18:11 ` Frank Rowand
2017-10-10 23:18 ` linux-next: No tree for Oct 10th Mark Brown
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=20171011125528.GI30097@localhost \
--to=vinod.koul@intel.com \
--cc=broonie@kernel.org \
--cc=cedric.madianga@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=pierre-yves.mordret@st.com \
--cc=rdunlap@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).