[PATCH] spi: spi: Remove unnecessary ‘0’ values from status

Li zeming posted 1 patch 1 year, 7 months ago
drivers/spi/spi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[PATCH] spi: spi: Remove unnecessary ‘0’ values from status
Posted by Li zeming 1 year, 7 months ago
status is assigned first, so it does not need to initialize the assignment.

Signed-off-by: Li zeming <zeming@nfschina.com>
---
 drivers/spi/spi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index bb731ab697a8..b1d85036d384 100644
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
@@ -3925,7 +3925,7 @@ static int spi_set_cs_timing(struct spi_device *spi)
 int spi_setup(struct spi_device *spi)
 {
 	unsigned	bad_bits, ugly_bits;
-	int		status = 0;
+	int		status;
 
 	/*
 	 * Check mode to prevent that any two of DUAL, QUAD and NO_MOSI/MISO
-- 
2.18.2
Re: [PATCH] spi: spi: Remove unnecessary ‘0’ values from status
Posted by Mark Brown 1 year, 7 months ago
On Mon, 08 Jul 2024 12:14:11 +0800, Li zeming wrote:
> status is assigned first, so it does not need to initialize the assignment.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi: Remove unnecessary ‘0’ values from status
      commit: 3bca1a3808a9674c410dcae2ca07fb3fbd74e614

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