linux-kernel - Re: linux-next: Tree for October 21 (staging/prism2-usb)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20081022045938.GB11458@kroah.com>
Date:	Tue, 21 Oct 2008 21:59:38 -0700
From:	Greg KH <greg@...ah.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for October 21 (staging/prism2-usb)

On Tue, Oct 21, 2008 at 09:47:20PM -0700, Randy Dunlap wrote:
> 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).

Hm, I added a WLAN_80211 dependancy here, which should catch this
problem (Ingo reported it a few days ago as well.)

Can you send me the config you used that caused this?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/