From: David Miller <davem@davemloft.net>
To: rdunlap@xenotime.net
Cc: shemminger@vyatta.com, sfr@canb.auug.org.au,
netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, sathya.perla@emulex.com,
subbu.seetharaman@emulex.com, ajit.khaparde@emulex.com
Subject: Re: linux-next: Tree for Aug 12 (benet/be2net)
Date: Fri, 12 Aug 2011 23:20:12 -0700 (PDT) [thread overview]
Message-ID: <20110812.232012.2290296405050164118.davem@davemloft.net> (raw)
In-Reply-To: <20110812151409.b8af0108.rdunlap@xenotime.net>
From: Randy Dunlap <rdunlap@xenotime.net>
Date: Fri, 12 Aug 2011 15:14:09 -0700
> On Fri, 12 Aug 2011 15:06:07 -0700 Stephen Hemminger wrote:
>
>> 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:
>
> That's really good news. It appears to be re-b0rked
> or this patch is not in linux-next yet.
Stephen Rothwell dropped the net-next tree from -next yesterday due to
some other unrelated fallout.
next prev parent reply other threads:[~2011-08-13 6:22 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
2011-08-12 22:14 ` Randy Dunlap
2011-08-13 6:20 ` David Miller [this message]
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=20110812.232012.2290296405050164118.davem@davemloft.net \
--to=davem@davemloft.net \
--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=shemminger@vyatta.com \
--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