Bluetooth: Use zero timeout for immediate scheduling

There's no point in passing a "small" timeout to queue_delayed_work() to
try to get the callback faster scheduled. Passing 0 is perfectly valid
and will cause a shortcut to a direct queue_work().

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

diff --git a/include/net/bluetooth/hci_core.h b/include/net/bluetooth/hci_core.h
index aa75eee8ad7fbe26f1b79a1a80de73e9b0e69553..18c24f6fce6c07598c2e77a60a3fef760d45e25f 100644 (file)
--- a/include/net/bluetooth/hci_core.h
+++ b/include/net/bluetooth/hci_core.h
@@ -791,7 +791,7 @@ static inline void hci_conn_drop(struct hci_conn *conn)
                                if (!conn->out)
                                        timeo *= 2;
                        } else {
-                               timeo = msecs_to_jiffies(10);
+                               timeo = 0;
                        }
                        break;
 
@@ -800,7 +800,7 @@ static inline void hci_conn_drop(struct hci_conn *conn)
                        break;
 
                default:
-                       timeo = msecs_to_jiffies(10);
+                       timeo = 0;
                        break;
                }