[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200802251319.03819.mb@bu3sch.de>
Date: Mon, 25 Feb 2008 13:19:03 +0100
From: Michael Buesch <mb@...sch.de>
To: "Pekka Enberg" <penberg@...helsinki.fi>
Cc: "Greg KH" <greg@...ah.com>,
"Alexey Zaytsev" <alexey.zaytsev@...il.com>,
"Ingo Molnar" <mingo@...e.hu>,
"Alexey Zaytsev" <zaytsev.a@...tei.ru>,
linux-kernel@...r.kernel.org,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: bcm43xx regression in 2.6.24 (with patch)
On Monday 25 February 2008 13:11:04 Pekka Enberg wrote:
> On Mon, Feb 25, 2008 at 11:54 AM, Michael Buesch <mb@...sch.de> wrote:
> > > Isn't the resolution Michael is suggesting is, "use the different driver"?
> >
> > I have two resolutions. One being:
> > rmmod b44
> > rmmod ssb
> > modprobe bcm43xx
> > modprobe b44
> >
> > The other being: Wait for 2.6.25 and use the maintained b43 driver.
>
> Neither of which seem like acceptable solutions for a 2.6.23 -> 2.6.24
> _regression_. Or maybe I am just too naive to believe Linus' statement
> on not letting the kernel regress...
So, please sign-off the patch that we have, if you think it's right
and doesn't cause more regressions.
--
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/
Powered by blists - more mailing lists