linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alex Dubov <oakad@yahoo.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mmc@vger.kernel.org
Subject: Re: linux-next: Tree for Nov 26 (mmc/host/tifm_sd.c)
Date: Mon, 26 Nov 2012 11:43:08 -0800	[thread overview]
Message-ID: <50B3C64C.1010801@infradead.org> (raw)
In-Reply-To: <20121127011738.9ecd7971a7ea2e3d09a9450d@canb.auug.org.au>

On 11/26/2012 06:17 AM, Stephen Rothwell wrote:

> Hi all,
> 
> Changes since 20121115:
> 


on i386:

drivers/built-in.o: In function `tifm_sd_request':
tifm_sd.c:(.text+0x588f95): undefined reference to `__udivdi3'


somewhere inside tifm_sd_request():

I'm guessing that the call to tifm_sd_set_data_timeout() was
inlined by gcc and it's the divide there that is the problem.

-- 

~Randy

  parent reply	other threads:[~2012-11-26 19:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-26 14:17 linux-next: Tree for Nov 26 Stephen Rothwell
2012-11-26 19:07 ` [PATCH -next] tty/serial: fix ifx6x60.c declaration warning Randy Dunlap
2012-11-26 19:43 ` Randy Dunlap [this message]
2012-11-26 20:56 ` linux-next: Tree for Nov 26 (staging/fwserial) Randy Dunlap
2012-11-26 23:20   ` Andrew Morton
2012-11-27  7:39     ` Peter Hurley
2012-11-27  7:11   ` [PATCH -next] staging/fwserial: Fix build breakage when !CONFIG_BUG Peter Hurley
2012-11-27 18:42     ` Randy Dunlap
2012-11-28  0:56       ` Peter Hurley
2012-11-27  7:17   ` linux-next: Tree for Nov 26 (staging/fwserial) Peter Hurley

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=50B3C64C.1010801@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=oakad@yahoo.com \
    --cc=sfr@canb.auug.org.au \
    /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).