Received-SPF: pass (google.com: domain of linux-kernel+bounces-67352-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
From: Mark Brown <broonie@kernel.org>
To: Serge Semin <fancer.lancer@gmail.com>, linux-spi@vger.kernel.org, 
 Colin Ian King <colin.i.king@gmail.com>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
In-Reply-To: <20240215131603.2062332-1-colin.i.king@gmail.com>
References: <20240215131603.2062332-1-colin.i.king@gmail.com>
Subject: Re: [PATCH][next] spi: dw: remove redundant assignment to variable
 len
Message-Id: <170801614725.198390.9313586989047610393.b4-ty@kernel.org>
Date: Thu, 15 Feb 2024 16:55:47 +0000
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

On Thu, 15 Feb 2024 13:16:03 +0000, Colin Ian King wrote:
> The variable id len being initialized with a value that is never read,
> 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]
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: dw: remove redundant assignment to variable len
      commit: 125b28b18926e050e770160a5897b81082304f8c

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark