summaryrefslogtreecommitdiff
path: root/tools/build/tests/ex/b.c
diff options
context:
space:
mode:
authorPing-Ke Shih <pkshih@realtek.com>2017-02-06 21:30:00 -0600
committerKalle Valo <kvalo@codeaurora.org>2017-02-07 09:25:08 +0200
commit6f85c03bc34ce7040f0b56eca963be4969b719de (patch)
treea54a5eb43e66796e40c630b5541146ebdecdcfd1 /tools/build/tests/ex/b.c
parent8d0d43e342083c9d2b15542e9a99727c0ef43a7f (diff)
rtlwifi: Add a new enumeration value to btc_set_type
The new value is needed for future capability. 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/build/tests/ex/b.c')
0 files changed, 0 insertions, 0 deletions
tected 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 'drivers/usb/chipidea/ci_hdrc_msm.c')