diff options
| author |   Nícolas F. R. A. Prado <nfraprado@collabora.com> | 2024-03-05 17:21:38 -0500 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2024-03-07 22:10:31 +0000 |
| commit | 6aeb8850e0f39869d43768603a75c0431562a429 (patch) | |
| tree | 8f8483c28247a05fb790043d75bb63fbf4bb6ffd | |
| parent | driver: core: Use dev_* instead of pr_* so device metadata is added (diff) | |
| download | wireguard-linux-6aeb8850e0f39869d43768603a75c0431562a429.tar.xz wireguard-linux-6aeb8850e0f39869d43768603a75c0431562a429.zip | |
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>
| -rw-r--r-- | drivers/base/dd.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/base/dd.c b/drivers/base/dd.c index d6e7933e2521..83d352394fdf 100644 --- a/drivers/base/dd.c +++ b/drivers/base/dd.c @@ -313,7 +313,7 @@ static void deferred_probe_timeout_work_func(struct work_struct *work) 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(); |