diff options
| author | Brian Norris <briannorris@chromium.org> | 2017-05-01 22:36:59 +0300 |
|---|---|---|
| committer | Kalle Valo <kvalo@codeaurora.org> | 2017-05-18 16:39:36 +0300 |
| commit | 21f569af9ab3608382482166ae9aba802b097e3f (patch) | |
| tree | 44297576b4af2fa52f4507eb1291a4c98cb410de /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | 83625a40165a01655db017fcc871c30e81e56ab4 (diff) | |
| download | linux-21f569af9ab3608382482166ae9aba802b097e3f.tar.xz | |
mwifiex: initiate card-specific work atomically
The non-atomic test + set is a little awkward here, and it technically
means we might double-schedule work unnecessarily. AFAICT, this is not
really a problem, since the extra "work" will be a no-op (the flag(s)
will be cleared by then), but it's still an anti-pattern.
Rewrite this to use the atomic test_and_set_bit() helper instead.
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions