Skip to contentSkip to conversation

spi: Fix cocci warnings

PATCH In review William Zhang 2 participants 2 messages Mar 7, 2023 SPI

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi: Fix cocci warnings

cocci reported warning: !A || A && B is equivalent to !A || B. This fix simplified the condition check to !A || B.

Fixes 76a85704cb91 ("spi: spi-mem: Allow controller supporting mem_ops without exec_op")

---

 drivers/spi/spi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi.c +1 -1
index 798030c0c5ce..503eb04826e7 100644
@@ -3076,7 +3076,7 @@ static int spi_controller_check_ops(struct spi_controller *ctlr)
 	 * If ->mem_ops or ->mem_ops->exec_op is NULL, we request that at least
 	 * one of the ->transfer_xxx() method be implemented.
 	 */
-	if (!ctlr->mem_ops || (ctlr->mem_ops && !ctlr->mem_ops->exec_op)) {
+	if (!ctlr->mem_ops || !ctlr->mem_ops->exec_op) {
 		if (!ctlr->transfer && !ctlr->transfer_one &&
 		   !ctlr->transfer_one_message) {
 			return -EINVAL;
Signature · 1 line
2.37.3
maintainer
#1 lore raw
Quoted 8 lines · William Zhang

cocci reported warning: !A || A && B is equivalent to !A || B. This fix simplified the condition check to !A || B.

Fixes 76a85704cb91 ("spi: spi-mem: Allow controller supporting mem_ops without exec_op")

[...]

Applied to

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

Thanks!

[1/1] spi: Fix cocci warnings

      commit: 20064c47f63e995216e0dfb0a6ea37b653ed534c

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