aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/check-perf-trace.py
diff options
context:
space:
mode:
authorLee Jones <[email protected]>2016-08-04 10:21:45 +0100
committerBjorn Andersson <[email protected]>2016-08-10 10:46:04 -0700
commit9c219b2337b87108cc57acf93e31ce1ab0e8013e (patch)
tree143c3b44379f0604a3a03bdaa41e5c518be9c06f /tools/perf/scripts/python/check-perf-trace.py
parent29b4817d4018df78086157ea3a55c1d9424a7cfc (diff)
remoteproc: core: Ensure error message is clear
Before this patch, the dma_alloc_coherent() failure path printed out: "dma_alloc_coherent err: 16760832" ... alluding to the Linux error code being 16760832, but seeing as Linux error codes are all negative, this looks like a signed/unsigned issue. In fact, the message is trying to print the length of the requested memory region. Let's clear that up. While we're at it, let's standardise the way 'len' is printed. In all other locations 'len' is in hex prefixed by a '0x' for clarity. Signed-off-by: Lee Jones <[email protected]> Signed-off-by: Bjorn Andersson <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions