staging: gasket: don't treat no device reset callback as an error
authorTodd Poynor <toddpoynor@google.com>
Fri, 20 Jul 2018 03:49:06 +0000 (20:49 -0700)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 21 Jul 2018 06:50:35 +0000 (08:50 +0200)
It is not an error for a device to not have a reset callback registered.

Signed-off-by: Simon Que <sque@chromium.org>
Signed-off-by: Todd Poynor <toddpoynor@google.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
drivers/staging/gasket/gasket_core.c

index 53236e1..eb5ad16 100644 (file)
@@ -1836,11 +1836,8 @@ int gasket_reset_nolock(struct gasket_dev *gasket_dev, uint reset_type)
        const struct gasket_driver_desc *driver_desc;
 
        driver_desc = gasket_dev->internal_desc->driver_desc;
-       if (!driver_desc->device_reset_cb) {
-               gasket_log_error(
-                       gasket_dev, "No device reset callback was registered.");
-               return -EINVAL;
-       }
+       if (!driver_desc->device_reset_cb)
+               return 0;
 
        /* Perform a device reset of the requested type. */
        ret = driver_desc->device_reset_cb(gasket_dev, reset_type);