spi: core: Initialize returned status in spi_setup
PATCH 1/1 spi: core: Initialize returned status in spi_setup
The previous commit that made bits-per-word validation conditional results in leaving no unconditional affectation of the status variable.
Since the variable is returned at the end of the function, initialize it to avoid returning an undefined value.
--- drivers/spi/spi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi.c +1 -1
@@ -3475,7 +3475,7 @@ static int __spi_validate_bits_per_word(struct spi_controller *ctlr,int spi_setup (struct spi_device *spi) {unsigned bad_bits, ugly_bits; -int status; +int status =0 ;/* * Check mode to prevent that any two of DUAL, QUAD and NO_MOSI/MISO
Signature · 1 line
2.35.1
Mark Brown
maintainerQuoted 8 lines · Paul Kocialkowski
The previous commit that made bits-per-word validation conditional results in leaving no unconditional affectation of the status variable.
Since the variable is returned at the end of the function, initialize it to avoid returning an undefined value.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: core: Initialize returned status in spi_setup
commit: 73f93db5c49b9f52c902e5dc6c750bf9832e0450
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