From: Randy Dunlap <rdunlap@infradead.org>
To: Jim Davis <jim.epost@gmail.com>
Cc: sfr@canb.auug.org.au, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, eli@mellanox.com
Subject: Re: randconfig build error with next-20130715, in drivers/net/ethernet/mellanox/mlx5/core
Date: Mon, 15 Jul 2013 10:32:42 -0700 [thread overview]
Message-ID: <51E4323A.3010903@infradead.org> (raw)
In-Reply-To: <20130715172614.GA4656@krebstar.arl.arizona.edu>
On 07/15/13 10:26, Jim Davis wrote:
> Building with the attached randcom configuration file, which sets
> CONFIG_X86_32=Y
>
> drivers/built-in.o: In function `average_read':
> debugfs.c:(.text+0x448e91): undefined reference to `__udivdi3'
> make: *** [vmlinux] Error 1
>
Hi,
You are the third person to report this.
Eli says that he has already fixed it, but a patch was just posted for
it earlier today.
thanks,
--
~Randy
prev parent reply other threads:[~2013-07-15 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 17:26 randconfig build error with next-20130715, in drivers/net/ethernet/mellanox/mlx5/core Jim Davis
2013-07-15 17:32 ` Randy Dunlap [this message]
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=51E4323A.3010903@infradead.org \
--to=rdunlap@infradead.org \
--cc=eli@mellanox.com \
--cc=jim.epost@gmail.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).