On Sat, Aug 01, 2009 at 03:11:25PM -0700, Marcel Holtmann wrote:

and that is what it should NOT imply. The policy if it applies to all
internal devices, all devices in general or just WiFi or Bluetooth for
example is up to the user.

We are NOT going to have any kind of RFKILL policy in the kernel in the
future. We will remove rfkill-input once we have a proper userspace
solution (aka rfkilld or similar).

We seem to be talking at cross purposes here. My objection to the name 
KEY_RFKILL is that it gives no indication what it's meant to be or why 
it's different to KEY_WLAN. KEY_RFKILL implies that it's the only input 
component that an rfkill policy agent needs to listen to, which isn't 
the case.

-- 
Matthew Garrett | mjg59@srcf.ucam.org