commit 6aeb8850e0f39869d43768603a75c0431562a429
author Nícolas F. R. A. Prado <nfraprado@collabora.com> Tue Mar 05 17:21:38 2024 -0500
committer Greg Kroah-Hartman <gregkh@linuxfoundation.org> Thu Mar 07 22:10:31 2024 +0000
tree 8f8483c28247a05fb790043d75bb63fbf4bb6ffd
parent 448af2d28899a2b4b1b07944b4910dfd5841bf55

device: core: Log warning for devices pending deferred probe on timeout

Once the deferred probe timeout has elapsed it is very likely that the
devices that are still deferring probe won't ever be probed. Therefore
log the defer probe pending reason at the warning level instead to bring
attention to the issue.

Signed-off-by: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Link: https://lore.kernel.org/r/20240305-device-probe-error-v1-3-a06d8722bf19@collabora.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

drivers/base/dd.c

diff --git a/drivers/base/dd.c b/drivers/base/dd.c
index d6e7933..83d3523 100644
--- a/drivers/base/dd.c
+++ b/drivers/base/dd.c
@@ -313,7 +313,7 @@
 
 	mutex_lock(&deferred_probe_mutex);
 	list_for_each_entry(p, &deferred_probe_pending_list, deferred_probe)
-		dev_info(p->device, "deferred probe pending: %s", p->deferred_probe_reason ?: "(reason unknown)\n");
+		dev_warn(p->device, "deferred probe pending: %s", p->deferred_probe_reason ?: "(reason unknown)\n");
 	mutex_unlock(&deferred_probe_mutex);
 
 	fw_devlink_probing_done();