diff options
| author | Lee Jones <[email protected]> | 2020-06-30 14:33:45 +0100 |
|---|---|---|
| committer | Linus Walleij <[email protected]> | 2020-07-08 09:24:08 +0200 |
| commit | a7a9ad232f02e6aa659cc9b58b72b1a30dccd1a6 (patch) | |
| tree | 1974858c72ff6bad3cf0b4b3e9edbec5341f6876 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 2f9bce5f38684cd10533ac41d8dd395a611cc8c5 (diff) | |
gpio: gpio-mlxbf2.c: Provide __releases() annotation to stop confusing Sparse
Sparse cannot peer into other functions to see when and if locks are
acquired and released, thus it simply warns that a 'context imbalance'
is detected instead. Let's be kind to Sparse and let it know that
this behaviour is intentional.
drivers/gpio/gpio-mlxbf2.c:125:12: warning: context imbalance in 'mlxbf2_gpio_lock_acquire' - different lock contexts for basic block
drivers/gpio/gpio-mlxbf2.c:151:13: warning: context imbalance in 'mlxbf2_gpio_lock_release' - unexpected unlock
Signed-off-by: Lee Jones <[email protected]>
Reviewed-by: Asmaa Mnebhi <[email protected]>
Cc: Asmaa Mnebhi <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Linus Walleij <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions