summaryrefslogtreecommitdiff
path: root/drivers/usb/musb
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2016-12-12 12:17:31 +0000
committerMark Brown <broonie@kernel.org>2016-12-12 12:17:31 +0000
commitd00b74613fb18dfd0a5aa99270ee2e72d5c808d7 (patch)
treea4a76197dc9cc07a9b64c3834bfc4f139f6447ef /drivers/usb/musb
parent56e3d92ddb97d9584622b29d4ecb268e30242b1e (diff)
parentf8192880a102849d84fe0f5e27bc8625a33e031c (diff)
parent3498c5e15db3af90aee7dbe9a0910225422b85c1 (diff)
Merge remote-tracking branches 'regulator/topic/tps65086' and 'regulator/topic/twl' into regulator-next
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-12-20 22:15:44 +0000
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 'net/dccp/ipv6.h')