From: Philip Langdale <philipl@overt.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
toshiba_acpi@memebeam.org, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill
Date: Mon, 28 Jul 2008 07:17:36 -0700 [thread overview]
Message-ID: <488DD500.1050805@overt.org> (raw)
In-Reply-To: <20080728030437.GC10672@khazad-dum.debian.net>
Henrique de Moraes Holschuh wrote:
>
> There is a bunch of rfkill bug fix patches that was not merged in
> wireless-testing yet (which is a pity, it would be really good if they could
> go into 2.6.27). One of those patches fixes the docs to make it clear that
> rfkill_force_state() is the way to go if you have events of any sort.
>
> The big difference from get_state() is that rfkill_force_state() propagates
> state changes as soon as your driver notices them and sends them to rfkill
> through rfkill_force_state()... while get_state() can only do that when
> someone asks rfkill about the current state.
Fair enough. I'll update the patch when I get some time. And good point on how
to react to the event; dunno what I was(n't) thinking. :-)
--phil
prev parent reply other threads:[~2008-07-28 14:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 18:17 [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill Philip Langdale
2008-07-27 20:59 ` Ivo van Doorn
2008-07-27 22:29 ` Philip Langdale
2008-07-28 3:04 ` Henrique de Moraes Holschuh
2008-07-28 11:17 ` Dan Williams
2008-07-28 18:52 ` Henrique de Moraes Holschuh
2008-07-28 20:32 ` Ivo van Doorn
2008-07-28 14:17 ` Philip Langdale [this message]
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=488DD500.1050805@overt.org \
--to=philipl@overt.org \
--cc=hmh@hmh.eng.br \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=toshiba_acpi@memebeam.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;
as well as URLs for NNTP newsgroup(s).