From: Randy Dunlap <randy.dunlap@oracle.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
swise@chelsio.com, LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org, general@lists.openfabrics.org
Subject: [ofa-general] Re: linux-next: Tree for February 9 (infiniband)
Date: Mon, 09 Feb 2009 09:01:11 -0800 [thread overview]
Message-ID: <49906157.9090707@oracle.com> (raw)
In-Reply-To: <49906118.3060801@opengridcomputing.com>
Steve Wise wrote:
> Randy Dunlap wrote:
>> Stephen Rothwell wrote:
>>
>>> Hi all,
>>>
>>> [I accidentally deleted the merge and quilt-import logs today :-( - I
>>> wonder if any would have noticed :-). The merge summary still appears
>>> below.]
>>>
>>> Changes since 20090206:
>>>
>>
>>
>> allyesconfig build on i386 fails with:
>>
>> drivers/built-in.o: In function `iwch_sgl2pbl_map':
>> /usr/builds/linux-next-20090209/drivers/infiniband/hw/cxgb3/iwch_qp.c:237:
>> undefined reference to `__umoddi3'
>> make: *** [.tmp_vmlinux1] Error 1
>>
>>
>> or allmodconfig on i386 fails with:
>>
>> ERROR: "__umoddi3" [drivers/infiniband/hw/cxgb3/iw_cxgb3.ko] undefined!
>>
>>
>
> Somehow changing offset to a u64 must have caused this. What is
> __umoddi3? (it can't be good) :)
It's some kind of mod operation, like 64-bit % 32-bit or
64-bit % 64-bit. Should be in a fairly recent change.
--
~Randy
next prev parent reply other threads:[~2009-02-09 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 8:39 linux-next: Tree for February 9 Stephen Rothwell
2009-02-09 16:53 ` [ofa-general] Re: linux-next: Tree for February 9 (infiniband) Randy Dunlap
2009-02-09 17:00 ` Steve Wise
2009-02-09 17:01 ` Randy Dunlap [this message]
2009-02-09 17:15 ` linux-next: Tree for February 9 (ide-dma) Randy Dunlap
2009-02-09 18:56 ` Bartlomiej Zolnierkiewicz
2009-02-09 21:50 ` Randy Dunlap
2009-02-09 21:38 ` [PATCH -next] alpha: fix link error re stacktrace Alexey Dobriyan
2009-02-09 21:55 ` Arnaldo Carvalho de Melo
2009-02-10 12:25 ` Ingo Molnar
2009-02-09 22:39 ` Ingo Molnar
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=49906157.9090707@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=swise@chelsio.com \
--cc=swise@opengridcomputing.com \
/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).