Hi Jia-Ju, > ath_wakeup_ar3k() is never called from atomic context. > > It is only called by ath_hci_uart_work() that is only called in > ath_open() via INIT_WORK(). > All of the above functions do not enter atomic context along the way. > > Despite never getting called from atomic context, ath_wakeup_ar3k() calls > mdelay() for busy wait. > That is not necessary and can be replaced with msleep to avoid busy wait. > > This is found by a static analysis tool named DCNS written by myself. > > Signed-off-by: Jia-Ju Bai <baijiaju1990@xxxxxxxxx> > --- > drivers/bluetooth/hci_ath.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) patch has been applied to bluetooth-next tree. Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
