summaryrefslogtreecommitdiff
path: root/include/rdma/opa_smi.h
diff options
context:
space:
mode:
authorPhilippe Reynes <tremyfr@gmail.com>2017-01-30 23:04:42 +0100
committerDavid S. Miller <davem@davemloft.net>2017-01-31 13:10:45 -0500
commitf8244ab55200dbe074380c3388804adff03a8a19 (patch)
treeafcd30800e83aba917466b3ef4e350f33aa1caf3 /include/rdma/opa_smi.h
parente9904990e8e70a51574e6ec6b872f3c705ec75f0 (diff)
net: aquantia: atlantic: use new api ethtool_{get|set}_link_ksettings
The ethtool api {get|set}_settings is deprecated. We move this driver to new api {get|set}_link_ksettings. As I don't have the hardware, I'd be very pleased if someone may test this patch. Signed-off-by: Philippe Reynes <tremyfr@gmail.com> Tested-by: Pavel Belous <pavel.s.belous@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/rdma/opa_smi.h')
0 files changed, 0 insertions, 0 deletions
lt, `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/dt-bindings/clock/oxsemi,ox820.h')