summaryrefslogtreecommitdiff
path: root/ifpps/.gitignore
diff options
context:
space:
mode:
authorStephen Wadeley <swadeley@redhat.com>2013-06-11 17:13:33 +0200
committerDaniel Borkmann <dborkman@redhat.com>2013-06-11 23:18:02 +0200
commit397483d79b222be420b7dc934e7751bb9d1829a6 (patch)
treed11fd32ec650c43e7ecd3997dc63da544853e9e4 /ifpps/.gitignore
parentf1e8419d9f5cf87570938fe5f4aafeb0e646478a (diff)
man: improvements to language for astraceroute.8
Signed-off-by: Stephen Wadeley <swadeley@redhat.com> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
Diffstat (limited to 'ifpps/.gitignore')
0 files changed, 0 insertions, 0 deletions
owski. First, I have replaced `pch->lock' with `pl330->lock' in functions `pl330_alloc_chan_resources' and `pl330_free_chan_resources'. This avoids the double-lock by 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 'include/drm/drm_connector.h')