iwlwifi: mvm: reduce usage of IEEE80211_SKB_CB() - net-next.git - net-next plumbings

summary refs log tree commit diff

path: root/drivers/usb/dwc2

diff options

author	Johannes Berg <johannes.berg@intel.com>	2016-12-02 13:33:40 +0100
committer	Luca Coelho <luciano.coelho@intel.com>	2017-02-03 16:26:41 +0200
commit	45b957e3edd22139a4e20067b39e15acbf36fb92 (patch)
tree	fbb347e77b52e704174385eec399a4abcd00c1f1 /drivers/usb/dwc2
parent	01796ff2fa6e81b0d806e735308d8171bcbfbec7 (diff)

iwlwifi: mvm: reduce usage of IEEE80211_SKB_CB()

There's already a variable with the result in scope, use that. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

Diffstat (limited to 'drivers/usb/dwc2')

0 files changed, 0 insertions, 0 deletions

ce_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 'tools/perf/scripts/python/compaction-times.py')