diff options
author | Johan Hovold <johan@hovoldconsulting.com> | 2016-06-27 20:07:10 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@google.com> | 2016-06-29 16:37:17 -0700 |
commit | 0b1d262354214daab1a3b7df763dc51c355ec353 (patch) | |
tree | 529b834a61785ebf9687c00516ff22294c7b8f8c /drivers/staging/greybus/es2.c | |
parent | a29bac623f015045385411eb9b3eced95aa96686 (diff) |
greybus: Revert "greybus: gb_connections_lock: don't use spin_lock_irq()"
This reverts commit b022fd95108e8b9d202532a74d39e86152bc8f7f.
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 <johan@hovoldconsulting.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Diffstat (limited to 'drivers/staging/greybus/es2.c')
0 files changed, 0 insertions, 0 deletions