diff options
author | Maciej S. Szmigiero <mail@maciej.szmigiero.name> | 2016-03-06 23:38:36 +0100 |
---|---|---|
committer | Darren Hart <dvhart@linux.intel.com> | 2016-03-23 10:05:51 -0700 |
commit | c7805e5459f5cac2d99e901e276908c205c3fd3a (patch) | |
tree | 0acfce67b2f4e9866445b243b2e35ad34a90a496 /scripts/Kbuild.include | |
parent | aaf3a5e77566ad186a85d28a0afd26b8dd0afd11 (diff) | |
download | talos-obmc-linux-c7805e5459f5cac2d99e901e276908c205c3fd3a.tar.gz talos-obmc-linux-c7805e5459f5cac2d99e901e276908c205c3fd3a.zip |
hp-wmi: fix unregister order in hp_wmi_rfkill_setup() once again
rfkill registration order in hp_wmi_rfkill_setup() is:
1) WiFi,
2) BT,
3) WWAN,
5) GPS.
Unregistration when cleaning up on error return should happen in reverse
order.
This means that: If BT rfkill fails to be allocated we possibly need to
first unregister WiFi rfkill before destroying it.
The same goes with (WWAN, BT) and (GPS, WWAN) pairs.
Also, if WWAN rfkill fails to register we need to (possibly) unregister BT
not the GPS one. And if GPS rfkill fails to register we need to unregister
WWAN not the BT one.
We never need to unregister GPS rfkill here since if GPS rfkill
registration succeeds this function returns without error so no cleanup is
necessary.
Signed-off-by: Maciej S. Szmigiero <mail@maciej.szmigiero.name>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Diffstat (limited to 'scripts/Kbuild.include')
0 files changed, 0 insertions, 0 deletions