crypto: inside-secure - initialize first_rdesc to make GCC happy

In the cipher safexcel_send_req function, GCC warns that
first_rdesc may be used uninitialized. While this should never
happen, this patch removes the warning by initializing this
variable to NULL to make GCC happy.

This was reported by the kbuild test robot.

Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

diff --git a/drivers/crypto/inside-secure/safexcel_cipher.c b/drivers/crypto/inside-secure/safexcel_cipher.c
index 54e0c615c4c80b034aa4846f2d751c4c60825dad..3aef1d43e43510130dc359d61c911e51209e9a7f 100644 (file)
--- a/drivers/crypto/inside-secure/safexcel_cipher.c
+++ b/drivers/crypto/inside-secure/safexcel_cipher.c
@@ -378,7 +378,7 @@ static int safexcel_send_req(struct crypto_async_request *base, int ring,
        struct safexcel_cipher_ctx *ctx = crypto_tfm_ctx(base->tfm);
        struct safexcel_crypto_priv *priv = ctx->priv;
        struct safexcel_command_desc *cdesc;
-       struct safexcel_result_desc *rdesc, *first_rdesc;
+       struct safexcel_result_desc *rdesc, *first_rdesc = NULL;
        struct scatterlist *sg;
        unsigned int totlen = cryptlen + assoclen;
        int nr_src, nr_dst, n_cdesc = 0, n_rdesc = 0, queued = totlen;