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

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 rc
Posted by Li zeming 1 year, 7 months ago
rc 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 fc13fa192189..bb731ab697a8 100644
--- a/drivers/spi/spi.c
+++ b/drivers/spi/spi.c
@@ -2594,7 +2594,7 @@ struct spi_device *spi_new_ancillary_device(struct spi_device *spi,
 {
 	struct spi_controller *ctlr = spi->controller;
 	struct spi_device *ancillary;
-	int rc = 0;
+	int rc;
 
 	/* Alloc an spi_device */
 	ancillary = spi_alloc_device(ctlr);
-- 
2.18.2
Re: [PATCH] spi: spi: Remove unnecessary ‘0’ values from rc
Posted by Mark Brown 1 year, 7 months ago
On Mon, 08 Jul 2024 11:53:20 +0800, Li zeming wrote:
> rc 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 rc
      commit: 0f2ecc3f6136a922f9d54499c80004bae6c42348

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