LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Larry Finger <larry.finger@lwfinger.net>,
Alexey Zaytsev <alexey.zaytsev@gmail.com>,
Stefano Brivio <stefano.brivio@polimi.it>,
Jeff Garzik <jgarzik@pobox.com>, Greg KH <greg@kroah.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix the bcm43xx driver breakage in 2.6.24/25.
Date: Wed, 27 Feb 2008 22:58:33 +0100 [thread overview]
Message-ID: <200802272258.33888.mb@bu3sch.de> (raw)
In-Reply-To: <20080227201550.GG3078@tuxdriver.com>
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.
next prev parent reply other threads:[~2008-02-27 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 13:17 [PATCH] Fix the bcm43xx driver breakage in 2.6.24/25 Alexey Zaytsev
2008-02-23 16:20 ` Michael Buesch
2008-02-23 20:37 ` Alexey Zaytsev
2008-02-24 16:26 ` Larry Finger
2008-02-27 20:15 ` John W. Linville
2008-02-27 21:58 ` Michael Buesch [this message]
2008-02-28 1:15 ` John W. Linville
2008-02-29 8:21 ` Andrew Morton
2008-02-29 10:05 ` Michael Buesch
2008-02-29 20:54 ` Ingo Molnar
2008-02-29 22:49 ` Michael Buesch
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=200802272258.33888.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=alexey.zaytsev@gmail.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=stefano.brivio@polimi.it \
/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;
as well as URLs for NNTP newsgroup(s).