Bluetooth: Add new hci_cb entries to the tail rather than the head

When processing hci_cb entries we want first registered callbacks to be
called first and later ones later. This is because eventually the L2CAP
callbacks that are part of the core will use this list and get
registered first. To keep the same order of calling L2CAP callbacks
before e.g. RFCOMM the order of elements needs to be this way.

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

diff --git a/net/bluetooth/hci_core.c b/net/bluetooth/hci_core.c
index 980260846d253a8f983eb352e11cf7a8f05b9e59..91f557b0318a26b3c32c48088fd9adf0fbaf1a76 100644 (file)
--- a/net/bluetooth/hci_core.c
+++ b/net/bluetooth/hci_core.c
@@ -3465,7 +3465,7 @@ int hci_register_cb(struct hci_cb *cb)
        BT_DBG("%p name %s", cb, cb->name);
 
        write_lock(&hci_cb_list_lock);
-       list_add(&cb->list, &hci_cb_list);
+       list_add_tail(&cb->list, &hci_cb_list);
        write_unlock(&hci_cb_list_lock);
 
        return 0;