device/connectivity: improve logging about cancelled connectivity check

There can be other reasons why the check was cancelled, not only because
the current item was obsoleted. For example, the caller who scheduled a
check externally, might have cancelled it or NMDevice might be
disposed().

1 files changed, 2 insertions, 2 deletions

diff --git a/src/devices/nm-device.c b/src/devices/nm-device.c
index e86e19709f..da4fe5bd52 100644
--- a/src/devices/nm-device.c
+++ b/src/devices/nm-device.c
@@ -2542,9 +2542,9 @@ concheck_cb (NMConnectivity *connectivity,
 
 	if (nm_utils_error_is_cancelled (error, FALSE)) {
 		/* the only place where we nm_connectivity_check_cancel(@c_handle), is
-		 * from inside concheck_handle_event(). This is a recursive call,
+		 * from inside concheck_handle_complete(). This is a recursive call,
 		 * nothing to do. */
-		_LOGT (LOGD_CONCHECK, "connectivity: complete check (seq:%llu, obsoleted by later request returning)",
+		_LOGT (LOGD_CONCHECK, "connectivity: complete check (seq:%llu, cancelled)",
 		       (long long unsigned) handle->seq);
 		return;
 	}