From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, gregkh <greg@kroah•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
netdev <netdev@vger•kernel.org>
Subject: Re: linux-next: Tree for October 31 (repeat build failures)
Date: Fri, 31 Oct 2008 13:28:39 -0700 [thread overview]
Message-ID: <20081031132839.8c07b0aa.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081031185613.7892fd8d.sfr@canb.auug.org.au>
On Fri, 31 Oct 2008 18:56:13 +1100 Stephen Rothwell wrote:
The only randconfig build failures that I see today (on i386 & x86_64)
are repeats of:
hp-plus undefined references:
http://marc.info/?l=linux-next&m=122513607505680&w=2
staging/go7007/go7007-v4l2:
http://marc.info/?l=linux-next&m=122513515404158&w=2
net/9p rdma_* undefined references with CONFIG_NET=y and CONFIG_INET=n:
http://marc.info/?l=linux-next&m=122504699904105&w=2
---
~Randy
next prev parent reply other threads:[~2008-10-31 20:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 7:56 linux-next: Tree for October 31 Stephen Rothwell
2008-10-31 20:28 ` Randy Dunlap [this message]
2008-11-01 10:44 ` Vegard Nossum
2008-11-03 15:16 ` Christoph Lameter
2008-11-04 0:28 ` Stephen Rothwell
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=20081031132839.8c07b0aa.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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