linux-kernel - Re: [PATCH][next] spi: dw: remove redundant assignment to variable len

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Thu, 15 Feb 2024 13:22:32 +0000
From: "Colin King (gmail)" <colin.i.king@...il.com>
To: Serge Semin <fancer.lancer@...il.com>, Mark Brown <broonie@...nel.org>,
 linux-spi@...r.kernel.org
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] spi: dw: remove redundant assignment to variable
 len

On 15/02/2024 13:16, Colin Ian King wrote:
> The variable id len being initialized with a value that is never read,

should be "len is being.."

> it is being re-assigned later on in a for-loop. The initialization is
> redundant and can be removed.
> 
> Cleans up clang scan build warning:
> drivers/spi/spi-dw-dma.c:580:17: warning: Although the value stored
> to 'len' is used in the enclosing expression, the value is never
> actually read from 'len' [deadcode.DeadStores]
> 
> Signed-off-by: Colin Ian King <colin.i.king@...il.com>
> ---
>   drivers/spi/spi-dw-dma.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/spi/spi-dw-dma.c b/drivers/spi/spi-dw-dma.c
> index 0ecbb6c36e23..f4c209e5f52b 100644
> --- a/drivers/spi/spi-dw-dma.c
> +++ b/drivers/spi/spi-dw-dma.c
> @@ -577,7 +577,7 @@ static int dw_spi_dma_transfer_one(struct dw_spi *dws,
>   	sg_init_table(&tx_tmp, 1);
>   	sg_init_table(&rx_tmp, 1);
>   
> -	for (base = 0, len = 0; base < xfer->len; base += len) {
> +	for (base = 0; base < xfer->len; base += len) {
>   		/* Fetch next Tx DMA data chunk */
>   		if (!tx_len) {
>   			tx_sg = !tx_sg ? &xfer->tx_sg.sgl[0] : sg_next(tx_sg);