spi: spi-cadence-quadspi: Fix missing unwind goto warnings
PATCH v2 1/1 spi: spi-cadence-quadspi: Fix missing unwind goto warnings
The following smatch warnings [0] were recently introduced:
drivers/spi/spi-cadence-quadspi.c:1882 cqspi_probe() warn: missing unwind goto?
Fix these warnings by releasing dma channel and adding a goto fail probe.
[0] https://lore.kernel.org/all/[email protected]/
---
Link to V1:
https://lore.kernel.org/all/[email protected]/
Changelog:
* added dma_release_channel
* added a fixes tag.
drivers/spi/spi-cadence-quadspi.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/spi/spi-cadence-quadspi.c +5 -2
@@ -1878,8 +1878,11 @@ static int cqspi_probe(struct platform_device *pdev) } ret =devm_pm_runtime_enable (dev); -if (ret) -return ret; +if (ret) { +if (cqspi->rx_chan) +dma_release_channel (cqspi->rx_chan); + goto probe_setup_failed; + }pm_runtime_set_autosuspend_delay (dev,CQSPI_AUTOSUSPEND_TIMEOUT );pm_runtime_use_autosuspend (dev);
base-commit: 21f252cd29f08892d48739fd7513ad79c1cff96a
Signature · 1 line
2.34.1
Quoted 8 lines · Dhruva Gole
The following smatch warnings [0] were recently introduced:
drivers/spi/spi-cadence-quadspi.c:1882cqspi_probe()warn: missing unwind goto?Fix these warnings by releasing dma channel and adding a goto fail probe.
Really this should be the Closes: link. I should edit the zero day bot emails to send the correct link.
That's going to be slightly more complicated than you might assume...
I'm travelling now so I won't do it today.
regards,
dan carpenter
Quoted 11 lines
Fixes 0578a6dbfe75 ("spi: spi-cadence-quadspi: add runtime pm support")Reported-by kernel test robot <[email protected]>Reported-by Dan Carpenter <[email protected]>Signed-off-by Dhruva Gole <[email protected]>---
Mark Brown
maintainerQuoted 4 lines · Dhruva Gole
The following smatch warnings [0] were recently introduced:
drivers/spi/spi-cadence-quadspi.c:1882cqspi_probe()warn: missing unwind goto?
This doesn't apply against current code, please check and resend.
Quoted 7 lines · Mark Brown
Quoted 4 lines · Dhruva Gole
The following smatch warnings [0] were recently introduced:
drivers/spi/spi-cadence-quadspi.c:1882cqspi_probe()warn: missing unwind goto?This doesn't apply against current code, please check and resend.
OK, will rebase and send along with the fixed closes tag.
Signature · 2 lines
Best regards, Dhruva Gole <[email protected]>
Quoted 7 lines · Mark Brown
Quoted 4 lines · Dhruva Gole
The following smatch warnings [0] were recently introduced:
drivers/spi/spi-cadence-quadspi.c:1882cqspi_probe()warn: missing unwind goto?This doesn't apply against current code, please check and resend.
Pardon, which branch is this being applied on?
I am on the following base and it applies OK:
commit b643e6268c8f466ebb08a594b8ec8a1e2fd275a2 (spi-broonie/for-next)
Merge: 3b4e5194138b da6de6d3ecc1
Author: Mark Brown <[email protected]>
Date: Tue Sep 26 13:08:30 2023 +0200
Merge remote-tracking branch 'spi/for-6.7' into spi-next
origin: spi-broonie https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
Signature · 2 lines
Best regards, Dhruva Gole <[email protected]>
Mark Brown
maintainerQuoted 1 line · Dhruva Gole
Pardon, which branch is this being applied on?
It'll have been applied as a fix so against 6.6.
Quoted 5 lines · Mark Brown
Quoted 1 line · Dhruva Gole
Pardon, which branch is this being applied on?
It'll have been applied as a fix so against 6.6.
Umm I don't think the commit being fixed is there in 6.6?
I am not really sure how I should base/format the patch? Please can you tell me what's expected in such a case ideally?
Signature · 2 lines
Best regards, Dhruva Gole <[email protected]>
Mark Brown
maintainerQuoted 3 lines · Dhruva Gole
Umm I don't think the commit being fixed is there in 6.6?
I am not really sure how I should base/format the patch? Please can you tell me what's expected in such a case ideally?
Including a full 12 character commit hash would help with matching, there were only 10 there. Not mix'n'matching Link:/Close: with links in the body of the commit message would help as well.
Quoted 7 lines · Mark Brown
Quoted 3 lines · Dhruva Gole
Umm I don't think the commit being fixed is there in 6.6?
I am not really sure how I should base/format the patch? Please can you tell me what's expected in such a case ideally?Including a full 12 character commit hash would help with matching,
I have given the full 12 chars, else checkpatch would've caught me :)
Quoted 2 lines
there were only 10 there. Not mix'n'matching Link:/Close: with links in the body of the commit message would help as well.
OK, I have fixed the links and sent the patch V3
Again, I have based on your for-next, as I don't see the fixes: commit in the 6.6 tree.
Signature · 2 lines
Best regards, Dhruva Gole <[email protected]>
Mark Brown
maintainerQuoted 8 lines · Dhruva Gole
The following smatch warnings [0] were recently introduced:
drivers/spi/spi-cadence-quadspi.c:1882cqspi_probe()warn: missing unwind goto?Fix these warnings by releasing dma channel and adding a goto fail probe.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: spi-cadence-quadspi: Fix missing unwind goto warnings
commit: 86401132d7bbb550d80df0959ad9fa356ebc168d
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