asus-wmi: update wlan LED through rfkill led trigger
On 08/28/2012 12:15 AM, AceLan Kao wrote:
> For this issue > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/901105 > > We need 2 patches from linux-next tree > > commit 06d7de831dab8b93adb86e039a2f3d36604a9197 > Author: AceLan Kao <acelan.kao@canonical.com> > 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 <acelan.kao@canonical.com> > Signed-off-by: Johannes Berg <johannes.berg@intel.com> > > commit 154a7a7b22342ab9ccde34f583e4b730965ee515 > Author: AceLan Kao <acelan.kao@canonical.com> > 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 <acelan.kao@canonical.com> > Signed-off-by: Matthew Garrett <mjg@redhat.com> > > Thanks. > Is there any reason we can't wait until these get merged upstream ? -- Tim Gardner tim.gardner@canonical.com -- kernel-team mailing list kernel-team@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kernel-team |
asus-wmi: update wlan LED through rfkill led trigger
Hi,
I just found those patches are hit linux-next tree, and Andy was asking to submit the patch to kernel-team, so I did it. Alright, I'll re-submit the SRU after those code getting merged upstream. Best regards, AceLan Kao. 2012/8/28 Tim Gardner <tim.gardner@canonical.com>: > On 08/28/2012 12:15 AM, AceLan Kao wrote: >> For this issue >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/901105 >> >> We need 2 patches from linux-next tree >> >> commit 06d7de831dab8b93adb86e039a2f3d36604a9197 >> Author: AceLan Kao <acelan.kao@canonical.com> >> 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 <acelan.kao@canonical.com> >> Signed-off-by: Johannes Berg <johannes.berg@intel.com> >> >> commit 154a7a7b22342ab9ccde34f583e4b730965ee515 >> Author: AceLan Kao <acelan.kao@canonical.com> >> 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 <acelan.kao@canonical.com> >> Signed-off-by: Matthew Garrett <mjg@redhat.com> >> >> Thanks. >> > > Is there any reason we can't wait until these get merged upstream ? > > -- > Tim Gardner tim.gardner@canonical.com -- Chia-Lin Kao(AceLan) http://blog.acelan.idv.tw/ E-Mail: acelan.kaoATcanonical.com (s/AT/@/) -- kernel-team mailing list kernel-team@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kernel-team |
| All times are GMT. The time now is 04:19 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.