Bluetooth: Use bt_dev_err and bt_dev_info when possible

In case of using BT_ERR and BT_INFO, convert to bt_dev_err and
bt_dev_info when possible. This allows for controller specific
reporting.

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

1 files changed, 2 insertions, 2 deletions

diff --git a/net/bluetooth/amp.c b/net/bluetooth/amp.c
index ebcab5bbadd7..78bec8df8525 100644
--- a/net/bluetooth/amp.c
+++ b/net/bluetooth/amp.c
@@ -187,7 +187,7 @@ int phylink_gen_key(struct hci_conn *conn, u8 *data, u8 *len, u8 *type)
 
         /* Legacy key */
         if (conn->key_type < 3) {
-                BT_ERR("Legacy key type %d", conn->key_type);
+                bt_dev_err(hdev, "legacy key type %d", conn->key_type);
                 return -EACCES;
         }
 
@@ -207,7 +207,7 @@ int phylink_gen_key(struct hci_conn *conn, u8 *data, u8 *len, u8 *type)
         /* Derive Generic AMP Link Key (gamp) */
         err = hmac_sha256(keybuf, HCI_AMP_LINK_KEY_SIZE, "gamp", 4, gamp_key);
         if (err) {
-                BT_ERR("Could not derive Generic AMP Key: err %d", err);
+                bt_dev_err(hdev, "could not derive Generic AMP Key: err %d", err);
                 return err;
         }