From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
xfs@oss.sgi.com
Subject: Re: linux-next: Tree for Jun 4 (radeonfb && xfs)
Date: Thu, 04 Jun 2015 19:15:18 +0000 [thread overview]
Message-ID: <5570A3C6.6050509@infradead.org> (raw)
In-Reply-To: <20150604231545.506332b5@canb.auug.org.au>
On 06/04/15 06:15, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20150603:
>
on i386:
fs/built-in.o: In function `xfs_ifree_cluster':
xfs_inode.c:(.text+0x1c491a): undefined reference to `__umoddi3'
drivers/built-in.o: In function `radeonfb_pci_register':
radeon_base.c:(.text+0x72fe0): undefined reference to `__divdi3'
--
~Randy
next parent reply other threads:[~2015-06-04 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150604231545.506332b5@canb.auug.org.au>
2015-06-04 19:15 ` Randy Dunlap [this message]
2015-06-04 23:00 ` linux-next: Tree for Jun 4 (radeonfb && xfs) Dave Chinner
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=5570A3C6.6050509@infradead.org \
--to=rdunlap@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=xfs@oss.sgi.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).