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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 07 May 2007 09:43:18 -0700 From: "Gary Zambrano" <zambrano@...adcom.com> To: "Jeff Garzik" <jeff@...zik.org> cc: "Michael Buesch" <mb@...sch.de>, "John Linville" <linville@...driver.com>, "Andrew Morton" <akpm@...ux-foundation.org>, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, bcm43xx-dev@...ts.berlios.de Subject: Re: Merging SSB upstream On Sat, 2007-05-05 at 23:11 -0400, Jeff Garzik wrote: > Michael Buesch wrote: > > So, now that mac80211 is merged upstream, I think it's > > time to merge SSB and the b44-ssb port upstream. > > Note that bcm43xx-mac80211 is _not_ ready for upstream, yet. > > > > What do you think? I'd like to merge ssb as-is, although > > the embedded-device parts are not quite finished, yet. > > But they don't interfere with the non-embedded parts used > > by b44 and the bcm43xx PCI cards. > > So we _could_ remove the ssb-mips code, but I don't like to > > do that for better maintainability. It doesn't hurt anyone IMO. > > What does Ralf (MIPS maintainer) and Gary (Broadcom maintainer) think? > > For my part, I'm not going to render even a tentative opinion without a > link to actual code. > > Last I saw of the code, and descriptions in IRC, it sounded sane. > > Jeff > I would like to put some test mileage behind the ssb. We had a hard time testing it a while back, so we will try the latest. Thanks, Gary - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists