summaryrefslogtreecommitdiff
path: root/drivers/bus/mvebu-mbus.c
diff options
context:
space:
mode:
authorAhmed S. Darwish <a.darwish@linutronix.de>2021-02-08 21:16:15 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2021-02-09 13:45:04 +0300
commita157270fbf37f822e1fa9e9faa8ed8c81da1eb28 (patch)
tree62730ddebfe1dad9bc08c085d0bbd2ddaaa491fb /drivers/bus/mvebu-mbus.c
parent151db8c08c90405c14384bbdc5acb136bc42dbf8 (diff)
downloadlinux-a157270fbf37f822e1fa9e9faa8ed8c81da1eb28.tar.xz
serial: core: Remove BUG_ON(in_interrupt()) check
The usage of in_interrupt() in drivers is phased out for various reasons. In both exported functions where BUG_ON(in_interrupt()) is invoked, there is a mutex_lock() afterwards. mutex_lock() contains a might_sleep() which will already trigger a stack trace if the target functions is called from atomic context. Remove the BUG_ON() and add a "Context: " in the kernel-doc instead. Signed-off-by: Ahmed S. Darwish <a.darwish@linutronix.de> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> Link: https://lore.kernel.org/r/20210208181615.381861-3-bigeasy@linutronix.de Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/bus/mvebu-mbus.c')
0 files changed, 0 insertions, 0 deletions