summaryrefslogtreecommitdiffstats
path: root/kernel/kprobes.c
diff options
context:
space:
mode:
authorNishanth Menon <nm@ti.com>2013-12-02 07:39:41 -0600
committerMichal Marek <mmarek@suse.cz>2014-01-03 14:39:35 +0100
commit79f0345fefaafb7cde301a830471edd21a37989b (patch)
tree5bc7dc2d1bbf6ab5df7d9f9b7a0457c73ac65033 /kernel/kprobes.c
parent37e2c2a775fc887acd1432908478dfd532f7f00f (diff)
downloadop-kernel-dev-79f0345fefaafb7cde301a830471edd21a37989b.zip
op-kernel-dev-79f0345fefaafb7cde301a830471edd21a37989b.tar.gz
scripts: Coccinelle script for pm_runtime_* return checks with IS_ERR_VALUE
As indicated by Sekhar in [1], there seems to be a tendency to use IS_ERR_VALUE to check the error result for pm_runtime_* functions which make no sense considering commit c48cd65 (ARM: OMAP: use consistent error checking) - the error values can either be < 0 for error OR 0, 1 in cases where we have success. So, setup a coccinelle script to help identify the same. [1] http://marc.info/?t=138472678100003&r=1&w=2 Cc: Russell King <rmk+kernel@arm.linux.org.uk> Reported-by: Sekhar Nori <nsekhar@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Acked-by: Julia Lawall <julia.lawall@lip6.fr> Signed-off-by: Michal Marek <mmarek@suse.cz>
Diffstat (limited to 'kernel/kprobes.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud