From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
gregkh <greg@kroah.com>
Subject: Re: linux-next: Tree for October 21 (staging/prism2-usb)
Date: Tue, 21 Oct 2008 21:47:20 -0700 [thread overview]
Message-ID: <20081021214720.a1ff0096.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20081021195109.ed83b102.sfr@canb.auug.org.au>
On Tue, 21 Oct 2008 19:51:09 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Today's tree will not build for powerpc allyesconfig (libc aborts the
> link due to a free() problem), sparc(32) defconfig and probably some
> other configurations.
>
> I am no longer commenting on conflicts that are clearly just caused by
> slight differences in what has been merged into Linus' tree and
> linux-next or conflicts caused by further changes in the linux-next after
> a subset of a tree has been merged.
ERROR: "wireless_send_event" [drivers/staging/wlan-ng/p80211.ko] undefined!
Looks like that driver should depend on WIRELESS or slt (something like that).
---
~Randy
next prev parent reply other threads:[~2008-10-22 4:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 8:51 linux-next: Tree for October 21 Stephen Rothwell
2008-10-21 12:07 ` Josh Boyer
2008-10-21 12:14 ` Stephen Rothwell
2008-10-21 13:02 ` Josh Boyer
2008-10-21 17:20 ` David Woodhouse
2008-10-21 22:55 ` Stephen Rothwell
2008-10-22 4:25 ` linux-next: Tree for October 21 (jffs2) Randy Dunlap
2008-10-22 4:47 ` Randy Dunlap [this message]
2008-10-22 4:59 ` linux-next: Tree for October 21 (staging/prism2-usb) Greg KH
2008-10-22 5:05 ` Randy Dunlap
2008-10-22 4:57 ` linux-next: Tree for October 21 (printk format warnings) Randy Dunlap
2008-10-22 5:01 ` Greg KH
2008-10-22 5:07 ` David Miller
2008-10-22 5:11 ` Randy Dunlap
2008-10-22 5:20 ` David Miller
2008-10-22 5:09 ` Randy Dunlap
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=20081021214720.a1ff0096.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=greg@kroah.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