From: Randy Dunlap <randy.dunlap@oracle.com>
To: David Vrabel <david.vrabel@csr.com>
Cc: Greg KH <greg@kroah.com>, lud <linux-usb@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for November 2 (usb/whci)
Date: Tue, 17 Nov 2009 07:51:01 -0800 [thread overview]
Message-ID: <20091117075101.0bf72415.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4B028BBB.1080803@csr.com>
On Tue, 17 Nov 2009 11:40:43 +0000 David Vrabel wrote:
> Greg KH wrote:
> > On Wed, Nov 11, 2009 at 09:04:03AM -0800, Randy Dunlap wrote:
> >> On Mon, 2 Nov 2009 09:13:39 -0800 Randy Dunlap wrote:
> >>
> >>> On Mon, 2 Nov 2009 17:38:45 +1100 Stephen Rothwell wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> Changes since 20091030: <<<<<<<<<<<<<<<<<<<<<<<<<<
> >>>
> >>> whci build fails on i386 due to 64-bit multiply & divide:
> >>>
> >>> ERROR: "__udivdi3" [drivers/usb/host/whci/whci-hcd.ko] undefined!
> >>> ERROR: "__umoddi3" [drivers/usb/host/whci/whci-hcd.ko] undefined!
> >>
> >> Still present in linux-next-20091111.
> >
> > David, can you please look into this and resolve it?
>
> Yes, I've been on holiday and haven't had a change to look into it yet.
>
> I can't immediately think of any 64 bit maths and I don't understand why
> I haven't seen it. I always build for i386.
When the driver is built-in (not a loadable module), the messages are:
drivers/built-in.o: In function `qset_add_urb':
(.text+0x4595f8): undefined reference to `__umoddi3'
drivers/built-in.o: In function `qset_add_urb':
(.text+0x45969a): undefined reference to `__udivdi3'
Those could still refer to other (inline) functions...
---
~Randy
next prev parent reply other threads:[~2009-11-17 15:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 6:38 linux-next: Tree for November 2 Stephen Rothwell
2009-11-02 9:12 ` [powerpc] Next tree Nov 2 : kernel BUG at mm/mmap.c:2135! Sachin Sant
2009-11-04 12:38 ` Sachin Sant
2009-11-05 0:16 ` David Gibson
2009-11-05 4:42 ` Sachin Sant
2009-11-12 11:16 ` Sachin Sant
2009-11-13 1:37 ` David Gibson
2009-11-13 2:10 ` David Gibson
2009-11-13 9:35 ` Sachin Sant
2009-11-17 5:25 ` David Gibson
2009-11-17 7:37 ` Sachin Sant
2009-11-18 2:36 ` David Gibson
[not found] ` <20091102173845.210d1c57.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2009-11-02 17:13 ` linux-next: Tree for November 2 (usb/whci) Randy Dunlap
2009-11-11 17:04 ` Randy Dunlap
[not found] ` <20091111090403.5fb0229e.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-11 17:30 ` Greg KH
2009-11-17 11:40 ` David Vrabel
2009-11-17 15:51 ` Randy Dunlap [this message]
[not found] ` <20091117075101.0bf72415.randy.dunlap-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2009-11-17 18:49 ` David Vrabel
2009-11-02 18:01 ` linux-next: Tree for November 2 (wireless/wl1271) Randy Dunlap
2009-11-02 18:44 ` John W. Linville
2009-11-02 18:48 ` John W. Linville
2009-11-02 21:10 ` Luciano Coelho
2009-11-03 6:03 ` Luciano Coelho
2009-11-07 10:37 ` Kalle Valo
2009-11-09 11:20 ` Luciano Coelho
2009-11-04 21:56 ` [PATCH] staging: RTL8192SU depends on USB Randy Dunlap
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=20091117075101.0bf72415.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=david.vrabel@csr.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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).