From: Fabio Estevam <fabio.este...@freescale.com>

Instead of propagating a 'fake' error code, just propagate the real
one in the case of caam_drv_identify_clk() failure.

Signed-off-by: Fabio Estevam <fabio.este...@freescale.com>
Reviewed-by: Horia Geantă <horia.gea...@freescale.com>
---
Changes since v2:
- None

 drivers/crypto/caam/ctrl.c | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/drivers/crypto/caam/ctrl.c b/drivers/crypto/caam/ctrl.c
index cd22849..b4124a6 100644
--- a/drivers/crypto/caam/ctrl.c
+++ b/drivers/crypto/caam/ctrl.c
@@ -440,7 +440,7 @@ static int caam_probe(struct platform_device *pdev)
                ret = PTR_ERR(clk);
                dev_err(&pdev->dev,
                        "can't identify CAAM ipg clk: %d\n", ret);
-               return -ENODEV;
+               return ret;
        }
        ctrlpriv->caam_ipg = clk;
 
@@ -449,7 +449,7 @@ static int caam_probe(struct platform_device *pdev)
                ret = PTR_ERR(clk);
                dev_err(&pdev->dev,
                        "can't identify CAAM mem clk: %d\n", ret);
-               return -ENODEV;
+               return ret;
        }
        ctrlpriv->caam_mem = clk;
 
@@ -458,7 +458,7 @@ static int caam_probe(struct platform_device *pdev)
                ret = PTR_ERR(clk);
                dev_err(&pdev->dev,
                        "can't identify CAAM aclk clk: %d\n", ret);
-               return -ENODEV;
+               return ret;
        }
        ctrlpriv->caam_aclk = clk;
 
@@ -467,7 +467,7 @@ static int caam_probe(struct platform_device *pdev)
                ret = PTR_ERR(clk);
                dev_err(&pdev->dev,
                        "can't identify CAAM emi_slow clk: %d\n", ret);
-               return -ENODEV;
+               return ret;
        }
        ctrlpriv->caam_emi_slow = clk;
 
-- 
1.9.1

--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to