linux-kernel - Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling through rfkill

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Jul 2008 07:17:36 -0700
From:	Philip Langdale <philipl@...rt.org>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
CC:	Ivo van Doorn <ivdoorn@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Matthew Garrett <mjg59@...f.ucam.org>,
	toshiba_acpi@...ebeam.org, linux-wireless@...r.kernel.org
Subject: Re: [PATCH 1/1] toshiba_acpi: Add support for bluetooth toggling
 through rfkill

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
--
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/