From: Stephen Hemminger <shemminger@vyatta.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
netdev <netdev@vger.kernel.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Sathya Perla <sathya.perla@emulex.com>,
Subbu Seetharaman <subbu.seetharaman@emulex.com>,
Ajit Khaparde <ajit.khaparde@emulex.com>
Subject: Re: linux-next: Tree for Aug 12 (benet/be2net)
Date: Fri, 12 Aug 2011 15:06:07 -0700 [thread overview]
Message-ID: <20110812150607.2303e10e@nehalam.ftrdhcpuser.net> (raw)
In-Reply-To: <20110812135618.a209d9af.rdunlap@xenotime.net>
On Fri, 12 Aug 2011 13:56:18 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Fri, 12 Aug 2011 17:13:11 +1000 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > [The kernel.org mirroring is being very slow today]
>
> [s.l.o.w.]
>
> > The net tree gained a build failure do I used the version from
> > next-20110811.
>
>
> On i386:
>
> drivers/built-in.o: In function `be_rx_eqd_update':
> be_main.c:(.text+0x569229): undefined reference to `__udivdi3'
>
Already fixed:
Author: Eric Dumazet <eric.dumazet@gmail.com> 2011-08-08 23:23:07
Committer: David S. Miller <davem@davemloft.net> 2011-08-12 02:54:22
Parent: 9aebddd11be42366f89b0296590770c02797aa98 (be2net: Move the Emulex driver)
Branches: master, remotes/origin/master
Follows: v3.0
Precedes:
benet: fix build error on 32bit arch
Error comes from commit ac124ff973e27802797
(be2net: cleanup and refactor stats code)
ERROR: "__udivdi3" [drivers/net/benet/be2net.ko] undefined!
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
CC: Sathya Perla <sathya.perla@emulex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2011-08-12 22:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110812171311.4d7bb640f38838bf7c34df50@canb.auug.org.au>
2011-08-12 20:56 ` linux-next: Tree for Aug 12 (benet/be2net) Randy Dunlap
2011-08-12 22:06 ` Stephen Hemminger [this message]
2011-08-12 22:14 ` Randy Dunlap
2011-08-13 6:20 ` David Miller
2011-08-13 6:19 ` David Miller
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=20110812150607.2303e10e@nehalam.ftrdhcpuser.net \
--to=shemminger@vyatta.com \
--cc=ajit.khaparde@emulex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sathya.perla@emulex.com \
--cc=sfr@canb.auug.org.au \
--cc=subbu.seetharaman@emulex.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