projects / platform / upstream / connman.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: de9a417) | patch
technology: Do not send any rfkill to kernel after receiving one 78/8278/3 tizen_ivi_genivi tizen_ivi_release accepted/tizen/20130912.082351 accepted/tizen/20130912.085336 accepted/tizen/20130912.093500 accepted/tizen/ivi/genivi/20140131.020206 accepted/tizen_ivi_release/20131120.050253 ivi_oct_m2 submit/tizen/20130815.011956 submit/tizen/20130912.075641 submit/tizen_ivi_genivi/20140131.015912 submit/tizen_ivi_release/20131120.032027
authorJukka Rissanen <jukka.rissanen@linux.intel.com>
Thu, 25 Jul 2013 13:31:29 +0000 (16:31 +0300)
committerZhang zhengguang <zhengguang.zhang@intel.com>
Thu, 15 Aug 2013 01:15:53 +0000 (09:15 +0800)
commit62da345484bba7397974de47c646ea2dc8af3b91
treea40e47088ee5602aca025691fad4b6cae2e8610etree | snapshot
parentde9a417f3ad6daf12eee7088570bc9f478e0f4cccommit | diff
technology: Do not send any rfkill to kernel after receiving one

If we receive rfkill event from kernel, we must not send it
back blindly. This could cause a ping-pong effect where the
technology is switched on/off constantly.

Upstream commit id:7a2d00e0bfe99cc327f78b9841bd8aca9efa2877
src/technology.c diff | blob | history
Domain: Network & Connectivity / Data Network;