diff options
author | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-25 07:35:46 +0100 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-02-27 18:03:53 -0800 |
commit | 21b0dc55bed6d9b5dd5d1ad22b75d9d1c7426bbc (patch) | |
tree | b3a65f1dd8feb9debbb17c407d97535ba8c5e351 /security | |
parent | 95cb0cb546c2892b7a31ff2fce6573f201a214b8 (diff) |
driver core: faux: only create the device if probe() succeeds
It's really hard to know if a faux device properly passes the callback
to probe() without having to poke around in the faux_device structure
and then clean up. Instead of having to have every user of the api do
this logic, just do it in the faux device core itself.
This makes the use of a custom probe() callback for a faux device much
simpler overall.
Suggested-by: Kurt Borja <kuurtb@gmail.com>
Cc: Rafael J. Wysocki <rafael@kernel.org>
Reviewed-by: Kurt Borja <kuurtb@gmail.com>
Reviewed-by: Danilo Krummrich <dakr@kernel.org>
Link: https://lore.kernel.org/r/2025022545-unroasted-common-fa0e@gregkh
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions