From: Mukesh Ojha <mojha@codeaurora.org>
To: Yue Haibing <yuehaibing@huawei.com>,
haren@us.ibm.com, herbert@gondor.apana.org.au,
davem@davemloft.net, benh@kernel.crashing.org, paulus@samba.org,
mpe@ellerman.id.au
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH -next] crypto: nx842 - remove set but not used variables 'dpadding' and 'max_sync_size'
Date: Sat, 30 Mar 2019 15:28:39 +0530 [thread overview]
Message-ID: <e69b2afd-8697-f51c-af4a-89b262f4d3d9@codeaurora.org> (raw)
In-Reply-To: <20190330055429.25848-1-yuehaibing@huawei.com>
On 3/30/2019 11:24 AM, Yue Haibing wrote:
> From: YueHaibing <yuehaibing@huawei.com>
>
> Fixes gcc '-Wunused-but-set-variable' warning:
>
> drivers/crypto/nx/nx-842.c: In function 'decompress':
> drivers/crypto/nx/nx-842.c:356:25: warning: variable 'dpadding' set but not used [-Wunused-but-set-variable]
> drivers/crypto/nx/nx-842-pseries.c: In function 'nx842_pseries_compress':
> drivers/crypto/nx/nx-842-pseries.c:299:15: warning: variable 'max_sync_size' set but not used [-Wunused-but-set-variable]
> drivers/crypto/nx/nx-842-pseries.c: In function 'nx842_pseries_decompress':
> drivers/crypto/nx/nx-842-pseries.c:430:15: warning: variable 'max_sync_size' set but not used [-Wunused-but-set-variable]
>
> They are not used any more and can be removed.
>
> Signed-off-by: YueHaibing <yuehaibing@huawei.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> drivers/crypto/nx/nx-842-pseries.c | 6 ++----
> drivers/crypto/nx/nx-842.c | 3 +--
> 2 files changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/crypto/nx/nx-842-pseries.c b/drivers/crypto/nx/nx-842-pseries.c
> index 6686997..5793284 100644
> --- a/drivers/crypto/nx/nx-842-pseries.c
> +++ b/drivers/crypto/nx/nx-842-pseries.c
> @@ -296,7 +296,7 @@ static int nx842_pseries_compress(const unsigned char *in, unsigned int inlen,
> struct nx842_workmem *workmem;
> struct nx842_scatterlist slin, slout;
> struct nx_csbcpb *csbcpb;
> - int ret = 0, max_sync_size;
> + int ret = 0;
> unsigned long inbuf, outbuf;
> struct vio_pfo_op op = {
> .done = NULL,
> @@ -319,7 +319,6 @@ static int nx842_pseries_compress(const unsigned char *in, unsigned int inlen,
> rcu_read_unlock();
> return -ENODEV;
> }
> - max_sync_size = local_devdata->max_sync_size;
> dev = local_devdata->dev;
>
> /* Init scatterlist */
> @@ -427,7 +426,7 @@ static int nx842_pseries_decompress(const unsigned char *in, unsigned int inlen,
> struct nx842_workmem *workmem;
> struct nx842_scatterlist slin, slout;
> struct nx_csbcpb *csbcpb;
> - int ret = 0, max_sync_size;
> + int ret = 0;
> unsigned long inbuf, outbuf;
> struct vio_pfo_op op = {
> .done = NULL,
> @@ -451,7 +450,6 @@ static int nx842_pseries_decompress(const unsigned char *in, unsigned int inlen,
> rcu_read_unlock();
> return -ENODEV;
> }
> - max_sync_size = local_devdata->max_sync_size;
> dev = local_devdata->dev;
>
> workmem = PTR_ALIGN(wmem, WORKMEM_ALIGN);
> diff --git a/drivers/crypto/nx/nx-842.c b/drivers/crypto/nx/nx-842.c
> index d94e25d..f06565d 100644
> --- a/drivers/crypto/nx/nx-842.c
> +++ b/drivers/crypto/nx/nx-842.c
> @@ -353,7 +353,7 @@ static int decompress(struct nx842_crypto_ctx *ctx,
> unsigned int adj_slen = slen;
> u8 *src = p->in, *dst = p->out;
> u16 padding = be16_to_cpu(g->padding);
> - int ret, spadding = 0, dpadding = 0;
> + int ret, spadding = 0;
> ktime_t timeout;
>
> if (!slen || !required_len)
> @@ -413,7 +413,6 @@ static int decompress(struct nx842_crypto_ctx *ctx,
> spadding = 0;
> dst = p->out;
> dlen = p->oremain;
> - dpadding = 0;
> if (dlen < required_len) { /* have ignore bytes */
> dst = ctx->dbounce;
> dlen = BOUNCE_BUFFER_SIZE;
next prev parent reply other threads:[~2019-03-30 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 5:54 Yue Haibing
2019-03-30 9:58 ` Mukesh Ojha [this message]
2019-04-08 6:41 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e69b2afd-8697-f51c-af4a-89b262f4d3d9@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=haren@us.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=yuehaibing@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®