summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/vm/Makefile
diff options
context:
space:
mode:
authorPing-Ke Shih <pkshih@realtek.com>2017-02-06 21:30:04 -0600
committerKalle Valo <kvalo@codeaurora.org>2017-02-07 09:25:08 +0200
commit0de9b5db9fbf70e8d9a98eae8cbdf33f7c04252c (patch)
tree89247507fbf855e28a3f9ab570af3dddb0522031 /tools/testing/selftests/vm/Makefile
parentdb8cb0095b0ec9700d6f369f594eb31ff683e322 (diff)
rtlwifi: move btcoex's ant_num declaration
File halbtcoutsrc.c is a better place for routine rtl_get_hwpg_ant_num() than file rtl_btc.c. Signed-off-by: Ping-Ke Shih <pkshih@realtek.com> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Diffstat (limited to 'tools/testing/selftests/vm/Makefile')
0 files changed, 0 insertions, 0 deletions
acquiring a different lock than `dma_pl330_rqcb'. NOTE that, as a result, `pl330_free_chan_resources' executes `list_splice_tail_init' on `pch->work_list' under lock `pl330->lock', whereas in the rest of the code `pch->work_list' is protected by `pch->lock'. I don't know if this may cause race conditions. Similarly `pch->cyclic' is written by `pl330_alloc_chan_resources' under `pl330->lock' but read by `pl330_tx_submit' under `pch->lock'. Second, I have removed locking from `pl330_request_channel' and `pl330_release_channel' functions. Function `pl330_request_channel' is only called from `pl330_alloc_chan_resources', so the lock is already held. Function `pl330_release_channel' is called from `pl330_free_chan_resources', which already holds the lock, and from `pl330_del'. Function `pl330_del' is called in an error path of `pl330_probe' and at the end of `pl330_remove', but I assume that there cannot be concurrent accesses to the protected data at those points. Signed-off-by: Iago Abal <mail@iagoabal.eu> Reviewed-by: Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'tools/power/cpupower/Makefile')