From: Will Keaney <keaneyw@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT v9] rfkill: rewrite
Date: Tue, 12 May 2009 13:26:08 -0400 [thread overview]
Message-ID: <4A09B130.9000106@gmail.com> (raw)
In-Reply-To: <1242030669.6930.10.camel@johannes.local>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
Johannes Berg wrote:
> This patch completely rewrites the rfkill core to address
> the following deficiencies:
>
> * all rfkill drivers need to implement polling where necessary
> rather than having one central implementation
>
> * updating the rfkill state cannot be done from arbitrary
> contexts, forcing drivers to use schedule_work and requiring
> lots of code
>
> * rfkill drivers need to keep track of soft/hard blocked
> internally -- the core should do this
>
> * the rfkill API has many unexpected quirks, for example being
> asymmetric wrt. alloc/free and register/unregister
>
> * rfkill can call back into a driver from within a function the
> driver called -- this is prone to deadlocks and generally
> should be avoided
>
> * rfkill-input pointlessly is a separate module
>
Please leave rfkill-input available as a module, at least until the bug
I reported in my previous e-mail 'Soft Lockup With rfkill_input and
thinkpad_acpi' is resolved. Otherwise it will render Thinkpads, and
possibly other systems, unusable with rfkill enabled.
Thank you,
Will Keaney
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2009-05-12 17:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 8:31 [RFT v9] rfkill: rewrite Johannes Berg
2009-05-12 14:09 ` Alan Jenkins
2009-05-13 10:49 ` Johannes Berg
2009-05-13 14:36 ` Alan Jenkins
2009-05-13 14:38 ` Johannes Berg
2009-05-13 21:48 ` Luis R. Rodriguez
2009-05-13 21:45 ` Luis R. Rodriguez
2009-05-14 9:02 ` Alan Jenkins
2009-05-14 9:08 ` Johannes Berg
2009-05-14 9:58 ` Alan Jenkins
2009-05-14 10:00 ` Johannes Berg
2009-05-14 4:34 ` Luis R. Rodriguez
2009-05-14 8:24 ` Alan Jenkins
2009-05-12 17:26 ` Will Keaney [this message]
2009-05-12 17:52 ` Johannes Berg
2009-05-12 17:59 ` Dan Williams
2009-05-12 18:04 ` Johannes Berg
2009-05-12 18:09 ` Will Keaney
2009-05-12 18:13 ` Johannes Berg
2009-05-13 21:40 ` Henrique de Moraes Holschuh
2009-05-13 22:19 ` Johannes Berg
2009-05-15 1:27 ` Henrique de Moraes Holschuh
2009-05-15 8:23 ` Johannes Berg
2009-05-18 11:00 ` Henrique de Moraes Holschuh
2009-05-19 12:12 ` Johannes Berg
2009-05-19 18:24 ` Henrique de Moraes Holschuh
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=4A09B130.9000106@gmail.com \
--to=keaneyw@gmail.com \
--cc=johannes@sipsolutions.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