[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080917153637.GD5186@khazad-dum.debian.net>
Date: Wed, 17 Sep 2008 12:36:37 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Larry Finger <Larry.Finger@...inger.net>
Cc: Michael Buesch <mb@...sch.de>,
Matthew Garrett <mjg59@...f.ucam.org>,
Carlos Corbacho <carlos@...angeworlds.co.uk>,
Adel Gadllah <adel.gadllah@...il.com>,
wireless <linux-wireless@...r.kernel.org>,
bcm43xx-dev@...ts.berlios.de, LKML <linux-kernel@...r.kernel.org>
Subject: Re: Regression in 2.6.27-rcX caused by commit
bc19d6e0b74ef03a3baf035412c95192b54dfc6f
On Wed, 17 Sep 2008, Larry Finger wrote:
> Henrique de Moraes Holschuh wrote:
> > He means rfkill_force_state() should change the LED state in the process,
> > which it isn't doing.
> >
> > It is an one-line patch, I am testing it now.
>
> If your one-line patch fixes my regression, then I'll ACK it for 2.6.27.
Sorry, it can't fix that regression by itself, since b43 is not using
rfkill_force_state() in mainline.
It will fix the same issue you are experiencing on b43 in anything that uses
rfkill_force_state(), which means (for mainline): iwlwifi, rt2x00,
thinkpad-acpi and hp-wmi.
It is a regression only on b43 and thinkpad-acpi, as the other drivers above
didn't use rfkill_force_state() in 2.6.26.
To fix the regression in b43, you'd be faced with the need of both my simple
patch AND Matthew's more complex one.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
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