summaryrefslogtreecommitdiff
path: root/ifpps/Makefile
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2013-06-14 17:02:44 +0200
committerTobias Klauser <tklauser@distanz.ch>2013-06-14 17:04:15 +0200
commit6224303b287dff9af046900841e43517479c37d0 (patch)
treeb433f489101f16d6fc66434635823dde66b061e3 /ifpps/Makefile
parent9d1ee4f333586967b75760226e781b1ebd181786 (diff)
netsniff-ng: Report if HW timestamping is enabled
Until now we didn't check the return value of set_sockopt_hwtimestamp() and the Coverity scanner complained about it, so use it's return value to report if timstamping is actually enabled in verbose mode. Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'ifpps/Makefile')
0 files changed, 0 insertions, 0 deletions
milarly `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 'sound/oss/soundcard.c')