man: manpage hyphen fixes, take two - netsniff-ng.git - A high-performance Linux networking toolkit

diff options

author	Kartik Mistry <kartik@debian.org>	2013-05-30 18:52:28 +0530
committer	Daniel Borkmann <dborkman@redhat.com>	2013-05-30 16:59:38 +0200
commit	802845c9f38e7ad05e879a4778d947ad3637d1d3 (patch)
tree	94158a69da41c84509c21c5ef1731bda61980f9d /curvetun/Makefile
parent	2e76c84b8e19ba02e82ce90370efe9feefd5a4b3 (diff)

man: manpage hyphen fixes, take two

Fix hyphens all over. Signed-off-by: Kartik Mistry <kartik@debian.org> Signed-off-by: Daniel Borkmann <dborkman@redhat.com>

Diffstat (limited to 'curvetun/Makefile')

0 files changed, 0 insertions, 0 deletions

ve 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 'net/openvswitch')


context:
space:
mode: