From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
dave.kleikamp@oracle.com
Subject: Re: linux-next: Tree for Sept 17 (jfs)
Date: Mon, 17 Sep 2012 08:46:23 -0700 [thread overview]
Message-ID: <505745CF.8040202@xenotime.net> (raw)
In-Reply-To: <20120917215938.11c456c113ac3b015cb2d5ae@canb.auug.org.au>
On 09/17/2012 04:59 AM, Stephen Rothwell wrote:
> Hi all,
>
> OK, so this was a bad one :-(
>
> Changes since 201209014:
>
> New tree: jfs
>
on i386:
modular build:
ERROR: "__divdi3" [fs/jfs/jfs.ko] undefined!
or builtin:
fs/built-in.o: In function `dbDiscardAG':
(.text+0x12988b): undefined reference to `__divdi3'
--
~Randy
next prev parent reply other threads:[~2012-09-17 15:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 11:59 linux-next: Tree for Sept 17 Stephen Rothwell
2012-09-17 15:46 ` Randy Dunlap [this message]
2012-09-17 16:50 ` linux-next: Tree for Sept 17 (jfs) Dave Kleikamp
2012-09-17 20:10 ` Geert Uytterhoeven
2012-09-17 17:33 ` [PATCH -next] staging: fix csr printk format warning 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=505745CF.8040202@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=dave.kleikamp@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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).