From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Re: b43 rfkill LED broken in 2.6.30-rc1 from wireless-testing
Date: Fri, 10 Apr 2009 09:32:07 +0200 [thread overview]
Message-ID: <1239348727.17031.15.camel@johannes.local> (raw)
In-Reply-To: <49DE6ABE.30207@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 361 bytes --]
Larry,
> Boy is the rfkill subsystem fragile.
>
> After all our debugging of the control of the b43 LED with the rfkill switch, it
> is broken again with 2.6.30-rc1.
Is that really _again_? My patch, which contained the fix, didn't go
into the tree yet, as I still need to fix up a few things and get
toshiba/sony/thinkpad converted :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-04-10 7:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-09 21:38 b43 rfkill LED broken in 2.6.30-rc1 from wireless-testing Larry Finger
2009-04-10 3:08 ` Larry Finger
2009-04-10 7:32 ` Johannes Berg [this message]
2009-04-11 6:19 ` Henrique de Moraes Holschuh
2009-04-11 10:43 ` Johannes Berg
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=1239348727.17031.15.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/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