diff options
| author | Andreas Fenkart <[email protected]> | 2015-07-17 09:13:06 +0200 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2015-08-06 10:09:13 +0300 |
| commit | c5bc15fce6aa33b7aeba4e049ceacfab66fa4a9f (patch) | |
| tree | f1d5cfd5d0ee3c7586666210f44b3a43f7330b29 /tools/perf/scripts/python | |
| parent | e9f21d403699a4d299a02df107326f11acecd13e (diff) | |
mwifiex: simplify mwifiex_complete_cmd
600f5d909a54("mwifiex: cleanup ioctl wait queue and abstraction layer")
introduced the wakeup_interruptible suppression in mwifiex_complete_cmd
b1a47aa5e1e1("mwifiex: fix system hang issue in cmd timeout error case")
then added wakup_interruptible to mwifiex_cmd_timeout_func the single
place setting a status of ETIMEDOUT.
Instead of doing extra work, using the standard call-chain will have the
same effect:
mwifiex_cancel_pending_ioctl
-> mwifiex_recycle_cmd_node
-> mwifiex_insert_cmd_to_free_q
-> mwifiex_complete_cmd
-> wake_up_interruptible
The difference is that previously the condition was not set to true,
but that's probably just an oversight in b1a47aa5e1e1 and shouldn't
have any consequence
Signed-off-by: Andreas Fenkart <[email protected]>
Acked-by: Amitkumar Karwar <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions