[PATCH 06/20] staging: gasket: don't treat no device reset callback as an error

[Todd Poynor]

From: Todd Poynor <toddpoy...@google.com>

It is not an error for a device to not have a reset callback registered.

Signed-off-by: Simon Que <s...@chromium.org>
Signed-off-by: Todd Poynor <toddpoy...@google.com>
---
 drivers/staging/gasket/gasket_core.c | 7 ++-----
 1 file changed, 2 insertions(+), 5 deletions(-)

diff --git a/drivers/staging/gasket/gasket_core.c 
b/drivers/staging/gasket/gasket_core.c
index 53236e1ba4e48..eb5ad161ccda2 100644
--- a/drivers/staging/gasket/gasket_core.c
+++ b/drivers/staging/gasket/gasket_core.c
@@ -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);
-- 
2.18.0.233.g985f88cf7e-goog