summaryrefslogtreecommitdiff
path: root/include/trace/events/random.h
diff options
context:
space:
mode:
authorGolan Ben-Ami <golan.ben.ami@intel.com>2017-01-25 15:11:30 +0200
committerLuca Coelho <luciano.coelho@intel.com>2017-02-08 17:54:23 +0200
commit0c8d0a4770cb6863f78a25c8d211f42e9c82251c (patch)
treebbc9d4510919dc5f259ab37a48b03cce6c9abe88 /include/trace/events/random.h
parentcd4d23c1ea9bb3769f2859b3b7b9ef24355bcba4 (diff)
iwlwifi: mvm: avoid exceeding the allowed print length
Divide a mfuart related print so it won't exceed the allowed MAX_MSG_LEN (110 bytes) per print. Fixes: 19f63c531b85 ("iwlwifi: mvm: support v2 of mfuart load notification") Signed-off-by: Golan Ben-Ami <golan.ben.ami@intel.com> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Diffstat (limited to 'include/trace/events/random.h')
0 files changed, 0 insertions, 0 deletions
'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/util/c++/clang.cpp')