summaryrefslogtreecommitdiff
path: root/src/bluetooth/qlowenergycontroller_bluez.cpp
diff options
context:
space:
mode:
authorJuha Vuolle <juha.vuolle@insta.fi>2021-09-13 08:45:17 +0300
committerJuha Vuolle <juha.vuolle@insta.fi>2021-09-17 08:20:24 +0300
commita82c068a8ce41f92816c015e9dc5957f7c3ec654 (patch)
tree4d66e620134227b384f2336e7129c76dc47da113 /src/bluetooth/qlowenergycontroller_bluez.cpp
parentab63bfa4efda42bbbf0fdca486911fec1817acc6 (diff)
downloadqtconnectivity-a82c068a8ce41f92816c015e9dc5957f7c3ec654.tar.gz
More consistent logging category use in bluetooth implementations
There were few plain qDebugs and qWarnings in the bluetooth code which content-wise seem indistinguishable from categorized logging in the same code. Pick-to: 6.2 Change-Id: I0a1a5c7fb14bd5d8b767a5f982ed5c2b3768f265 Reviewed-by: Alex Blasche <alexander.blasche@qt.io>
Diffstat (limited to 'src/bluetooth/qlowenergycontroller_bluez.cpp')
-rw-r--r--src/bluetooth/qlowenergycontroller_bluez.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/bluetooth/qlowenergycontroller_bluez.cpp b/src/bluetooth/qlowenergycontroller_bluez.cpp
index 5600be4b..5c2b30ec 100644
--- a/src/bluetooth/qlowenergycontroller_bluez.cpp
+++ b/src/bluetooth/qlowenergycontroller_bluez.cpp
@@ -1843,7 +1843,7 @@ int QLowEnergyControllerPrivateBluez::securityLevel() const
if (optval & L2CAP_LM_SECURE)
level = BT_SECURITY_HIGH;
- qDebug() << "Current l2cp sec level (old):" << level;
+ qCDebug(QT_BT_BLUEZ) << "Current l2cp sec level (old):" << level;
return level;
}
@@ -1890,7 +1890,7 @@ bool QLowEnergyControllerPrivateBluez::setSecurityLevel(int level)
}
if (setsockopt(socket, SOL_L2CAP, L2CAP_LM, &optval, sizeof(optval)) == 0) {
- qDebug(QT_BT_BLUEZ) << "Old l2cp sec level:" << optval;
+ qCDebug(QT_BT_BLUEZ) << "Old l2cp sec level:" << optval;
return true;
}