driver: core: Log probe failure as error and with device metadata
authorNícolas F. R. A. Prado <nfraprado@collabora.com>
Tue, 5 Mar 2024 22:21:36 +0000 (17:21 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 7 Mar 2024 22:10:31 +0000 (22:10 +0000)
commit32de4b4f9dfa67917d2cc824a195498513ec8e8d
tree3f291cbaa25eff45d5ddb2d3d5fb4640ec88b870
parent135116f3d01402b610e00dd54f3b059a3faf35de
driver: core: Log probe failure as error and with device metadata

Drivers can return -ENODEV or -ENXIO from their probe to reject a device
match, and return -EPROBE_DEFER if probe should be retried. Any other
error code is not expected during normal behavior and indicates an
issue occurred, so it should be logged at the error level.

Also make use of the device variant, dev_err(), so that the device
metadata is attached to the log message.

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