[PATCH] spi: spi-mem: Introduce a default ->exec_op() debug log

[Mark Brown]

On Wed, Mar 19, 2025 at 05:56:28PM +0100, Miquel Raynal wrote:

> I'd say that for this particular purpose I do not thing that trace
> printks or events would really fit. As a developer, I'd definitely
> always change the function calls to some direct printk calls in this
> case. The verbose debug alternative seduced me though, so if that's okay
> for you, I'll switch to dev_vdgb() as suggested by Tudor, which honestly
> feels like a seducing alternative.

That's fine for me.  I do have to say that I tend to end up doing the
opposite of you and adding tracepoints to code I'm doing much with, they
work so much better so long as you can get the buffer off the device.
Low overhead, much bigger lookback and better tooling.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-mtd/attachments/20250319/71725544/attachment.sig>