| 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
| ||
|
Date: Sat, 5 May 2007 22:00:51 -0400 From: "John W. Linville" <linville@...driver.com> To: Michael Buesch <mb@...sch.de> Cc: Jeff Garzik <jeff@...zik.org>, Andrew Morton <akpm@...ux-foundation.org>, Gary Zambrano <zambrano@...adcom.com>, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, bcm43xx-dev@...ts.berlios.de, ralf@...ux-mips.org Subject: Re: Merging SSB upstream On Sun, May 06, 2007 at 03:03:17AM +0200, 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. ACK, unfortunately. > 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. How much testing have you (and others) done w/ b44? I had to remove the b44 ssb changes from fedora because a) users reported problems; and b) I was more worried about wireless than b44+ssb. (sorry!) So, has anyone been using b44 in -mm? > 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. I guess I don't see a problem w/ merging the mips part, as long as the b44 part has been thoroughly tested. I wonder if Ralf has an opinion? John -- John W. Linville linville@...driver.com - 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