aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorRicardo Silva <[email protected]>2017-05-15 10:18:14 +0100
committerGreg Kroah-Hartman <[email protected]>2017-05-16 13:53:23 +0200
commit9d156621751094293e9739debd77cc4751ba2dcf (patch)
tree18a561a63d9e5c5e4667e5a1c2c96b83af559a4c /tools/perf/scripts/python/call-graph-from-postgresql.py
parentd7206352fc327eb833e137739269022a1e6c0a7f (diff)
staging: vme: Use BIT macro for bit definitions
Use the BIT(n) macro instead of '(1 << n)' in definitions where the bit semantics clearly applies. Fixes true positive "Prefer using the BIT macro" checks reported by checkpatch. Some of these checks are still triggering on definitions using '(1 << n)', namely for PIO2_CNTR_SC_DEV1, PIO2_CNTR_RW_LSB and PIO2_CNTR_MODE1. Leave them be, as the context there is more of a "multi-bit field value" ((val << n), where for some cases 'val' happens to be 1) rather than a "single bit" (1 << n), so keeping the value as is in the code makes it more readable that using a combination of BIT macros. Signed-off-by: Ricardo Silva <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions