linux-kernel - Re: [PATCH] Fix the bcm43xx driver breakage in 2.6.24/25.

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: <200802272258.33888.mb@bu3sch.de>
Date:	Wed, 27 Feb 2008 22:58:33 +0100
From:	Michael Buesch <mb@...sch.de>
To:	"John W. Linville" <linville@...driver.com>
Cc:	Larry Finger <larry.finger@...inger.net>,
	Alexey Zaytsev <alexey.zaytsev@...il.com>,
	Stefano Brivio <stefano.brivio@...imi.it>,
	Jeff Garzik <jgarzik@...ox.com>, Greg KH <greg@...ah.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix the bcm43xx driver breakage in 2.6.24/25.

On Wednesday 27 February 2008 21:15:50 John W. Linville wrote:
> On Sun, Feb 24, 2008 at 09:26:34AM -0700, Larry Finger wrote:
> 
> > I have reviewed the above patches and tested them with what I believe to be 
> > most combinations. Everything worked and corrected the unintended 
> > consequence of breaking bcm43xx when b44 is included. I agree that these 
> > patches belong in 2.6.25 and stable (2.6.24). Of course, the problem goes 
> > away in 2.6.26.
> 
> I can't say I really like Alexey's patches, but I guess they are OK.
> I think I like the "b43_pci_bridge as a module" option a little better,
> but as Michael illustrated there are problems with that approach too.

Well, I do like  "b43_pci_bridge as a module" more than this inter-dependency
crap. Yeah, I don't like "b43_pci_bridge as a module" a lot, but certainly
more than Alexey's patch.

-- 
Greetings Michael.
--
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/