[PATCH] spi: stm32-ospi: Remove exec_op() callback debug log

[PATCH] spi: stm32-ospi: Remove exec_op() callback debug log

[Patrice Chotard]

Since commit ad4488845193 ("spi: spi-mem: Introduce a default ->exec_op()
debug log") a common debug log is available in spi-mem, so remove the one
from spi-stm32-ospi driver.

Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
---
 drivers/spi/spi-stm32-ospi.c | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/drivers/spi/spi-stm32-ospi.c b/drivers/spi/spi-stm32-ospi.c
index f36fd36da269..f44a42301ea4 100644
--- a/drivers/spi/spi-stm32-ospi.c
+++ b/drivers/spi/spi-stm32-ospi.c
@@ -441,11 +441,6 @@ static int stm32_ospi_send(struct spi_device *spi, const struct spi_mem_op *op)
 	int timeout, err = 0, err_poll_status = 0;
 	u8 cs = spi->chip_select[ffs(spi->cs_index_mask) - 1];
 
-	dev_dbg(ospi->dev, "cmd:%#x mode:%d.%d.%d.%d addr:%#llx len:%#x\n",
-		op->cmd.opcode, op->cmd.buswidth, op->addr.buswidth,
-		op->dummy.buswidth, op->data.buswidth,
-		op->addr.val, op->data.nbytes);
-
 	cr = readl_relaxed(ospi->regs_base + OSPI_CR);
 	cr &= ~CR_CSSEL;
 	cr |= FIELD_PREP(CR_CSSEL, cs);

---
base-commit: 05f7e89ab9731565d8a62e3b5d1ec206485eeb0b
change-id: 20260213-upstream_ospi_remove_exec_op_debug_log-e5c5ffc26922

Best regards,
-- 
Patrice Chotard <patrice.chotard@foss.st.com>

Re: [PATCH] spi: stm32-ospi: Remove exec_op() callback debug log

[Mark Brown]

On Fri, 13 Feb 2026 09:19:11 +0100, Patrice Chotard wrote:
> Since commit ad4488845193 ("spi: spi-mem: Introduce a default ->exec_op()
> debug log") a common debug log is available in spi-mem, so remove the one
> from spi-stm32-ospi driver.
> 
> 

Applied to

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

Thanks!

[1/1] spi: stm32-ospi: Remove exec_op() callback debug log
      commit: 52531750d39b94803e089dda95e43925730c03bd

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