From: Larry Finger <Larry.Finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Inaky Perez-Gonzalez <inaky@linux.intel.com>,
Dirk Opfer <Dirk@Opfer-Online.de>,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [RFC v6] rfkill: rewrite
Date: Tue, 14 Apr 2009 23:34:10 -0500 [thread overview]
Message-ID: <49E563C2.8030502@lwfinger.net> (raw)
In-Reply-To: <1239750483.4205.28.camel@johannes.local>
Johannes Berg wrote:
> This patch completely rewrites the rfkill core to address
> the following deficiencies:
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
> ---
> v3: * fix locking bugs
> * fix bug in input.c that made it ignore things
> * allow setting LED trigger name
> * apply default state while registering
> * convert HSO
> v4: * LED triggering
> v5: * convert sony
> * introduce rfkill_set_states function
> * change query/poll methods to require calls to
> rfkill_set{_sw,_hw}_state/rfkill_set_states
> * do not call driver from registration
> * remove tested-by since it changed a lot
> v6: * fix stupid sync work bugs
V6 works with b43legacy.
Tested-by: Larry Finger <Larry.Finger@lwfinger.net>
next prev parent reply other threads:[~2009-04-15 4:34 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 17:53 [RFC] rfkill: rewrite Johannes Berg
2009-03-29 18:16 ` Ivo van Doorn
2009-03-30 13:27 ` Henrique de Moraes Holschuh
2009-03-30 9:06 ` Johannes Berg
2009-03-30 9:54 ` Michael Buesch
2009-03-30 9:57 ` Johannes Berg
2009-03-30 10:39 ` Johannes Berg
2009-03-30 9:40 ` Johannes Berg
2009-03-30 10:04 ` Matthew Garrett
2009-03-30 13:29 ` Henrique de Moraes Holschuh
2009-03-30 14:08 ` Johannes Berg
2009-03-30 17:34 ` Henrique de Moraes Holschuh
2009-03-30 17:41 ` Johannes Berg
2009-03-30 20:48 ` Henrique de Moraes Holschuh
2009-03-30 20:52 ` Johannes Berg
2009-03-30 21:02 ` Henrique de Moraes Holschuh
2009-03-30 21:20 ` Johannes Berg
2009-03-30 17:39 ` Inaky Perez-Gonzalez
2009-03-30 17:45 ` Johannes Berg
2009-03-30 17:54 ` Ivo van Doorn
2009-03-30 18:00 ` Johannes Berg
2009-03-30 20:36 ` Inaky Perez-Gonzalez
2009-03-30 20:43 ` Johannes Berg
2009-03-30 20:52 ` Henrique de Moraes Holschuh
2009-03-30 19:01 ` Johannes Berg
2009-03-30 22:07 ` Johannes Berg
2009-03-30 22:08 ` Johannes Berg
2009-03-30 21:15 ` Henrique de Moraes Holschuh
2009-03-30 21:26 ` Johannes Berg
2009-03-30 21:26 ` Johannes Berg
2009-04-05 14:59 ` Henrique de Moraes Holschuh
2009-04-07 10:36 ` Johannes Berg
2009-04-08 18:06 ` Henrique de Moraes Holschuh
2009-04-14 21:03 ` Johannes Berg
2009-03-30 22:16 ` [RFC/RFT v2] " Johannes Berg
2009-03-30 23:20 ` Larry Finger
2009-03-31 8:02 ` Johannes Berg
2009-03-31 8:11 ` Johannes Berg
2009-03-31 12:16 ` Johannes Berg
2009-03-31 18:20 ` Larry Finger
2009-03-31 18:32 ` Johannes Berg
2009-03-31 19:11 ` [RFC v3] " Johannes Berg
2009-04-14 21:48 ` [RFC v5] " Johannes Berg
2009-04-14 23:08 ` [RFC v6] " Johannes Berg
2009-04-15 4:34 ` Larry Finger [this message]
2009-04-30 3:19 ` Henrique de Moraes Holschuh
2009-04-30 8:53 ` Johannes Berg
2009-04-30 14:11 ` Henrique de Moraes Holschuh
2009-04-30 14:18 ` Johannes Berg
2009-04-30 15:06 ` Johannes Berg
2009-04-30 15:53 ` Henrique de Moraes Holschuh
2009-04-30 16:09 ` Johannes Berg
2009-04-30 15:14 ` [RFC v8] " 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=49E563C2.8030502@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Dirk@Opfer-Online.de \
--cc=hmh@hmh.eng.br \
--cc=inaky@linux.intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg@redhat.com \
/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).