Comment 16 for bug 901105

The required patches are in 3.5 and 3.8 mainstream kernel.

commit 06d7de831dab8b93adb86e039a2f3d36604a9197
Author: AceLan Kao <email address hidden>
Date: Thu Jul 26 09:51:08 2012 +0800

    Revert "rfkill: remove dead code"

    This reverts commit 2e48928d8a0f38c1b5c81eb3f1294de8a6382c68.

    Those functions are needed and should not be removed, or
    there is no way to set the rfkill led trigger name.

    Signed-off-by: AceLan Kao <email address hidden>
    Signed-off-by: Johannes Berg <email address hidden>

commit 6cae06e603339f99334bc6b276e2ac619cf0d476
Author: AceLan Kao <email address hidden>
Date: Fri Jul 27 16:51:59 2012 +0800

    asus-wmi: update wlan LED through rfkill led trigger

    For those machines with wapf=4, BIOS won't update the wireless LED,
    since wapf=4 means user application will take in chage of the wifi and bt.
    So, we have to update wlan LED status explicitly.

    But I found there is another wireless LED bug in launchpad and which is
    not in the wapf=4 quirk.
    So, it might be better to set wireless LED status explicitly for all
    machines.

    BugLink: https://launchpad.net/bugs/901105

    Signed-off-by: AceLan Kao <email address hidden>
    Signed-off-by: Matthew Garrett <email address hidden>