aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJohan Hovold <[email protected]>2016-06-27 20:07:11 +0200
committerGreg Kroah-Hartman <[email protected]>2016-06-29 16:37:17 -0700
commit07af934094ed7d79442dcec82305001e3a66ad6c (patch)
tree10ca49bdfd1a4478cade3ca7955b2dbeb0a5c67f /tools/perf/scripts/python
parent0b1d262354214daab1a3b7df763dc51c355ec353 (diff)
greybus: Revert "greybus: es2.c: don't use spin_lock_irq()"
This reverts commit b44c3b5b0307788750eb4c462ed5982236876a8b. Someone decided that all use of spin_lock_irq was to be considered a bug and went on a search-and-replace type "bug-fixing" spree last week. This is however just plain wrong. Using spin_lock_irq is perfectly fine in paths were interrupts have not been disabled, and this is in fact even preferred over the lazy approach of always using spin_lock_irqsave instead of understanding the code that is being written or modified. All current uses of spin_lock_irq have already been vetted in this respect. Also note that it is only used in functions that may sleep, that is, in functions that must not be called with interrupts disabled in the first place. Signed-off-by: Johan Hovold <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions