There's an easier way to get at the hash transform - rather than
using crypto_ahash_tfm(ahash), we can get it directly from
req->base.tfm.

Signed-off-by: Russell King <rmk+ker...@arm.linux.org.uk>
---
 drivers/crypto/marvell/hash.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/crypto/marvell/hash.c b/drivers/crypto/marvell/hash.c
index a24ceda7acfe..d9cc49e9c43b 100644
--- a/drivers/crypto/marvell/hash.c
+++ b/drivers/crypto/marvell/hash.c
@@ -803,7 +803,7 @@ static int mv_cesa_ahash_export(struct ahash_request *req, 
void *hash,
        unsigned int digsize = crypto_ahash_digestsize(ahash);
        unsigned int blocksize;
 
-       blocksize = crypto_tfm_alg_blocksize(crypto_ahash_tfm(ahash));
+       blocksize = crypto_tfm_alg_blocksize(req->base.tfm);
 
        *len = creq->len;
        memcpy(hash, creq->state, digsize);
@@ -828,7 +828,7 @@ static int mv_cesa_ahash_import(struct ahash_request *req, 
const void *hash,
        if (ret)
                return ret;
 
-       blocksize = crypto_tfm_alg_blocksize(crypto_ahash_tfm(ahash));
+       blocksize = crypto_tfm_alg_blocksize(req->base.tfm);
        if (len >= blocksize)
                mv_cesa_update_op_cfg(&creq->op_tmpl,
                                      CESA_SA_DESC_CFG_MID_FRAG,
-- 
2.1.0

--
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