Thomas Weißschuh 6e6d3c6f0e dmaengine: stm32: Don't use %pK through printk ... In the past %pK was preferable to %p as it would not leak raw pointer values into the kernel log. Since commit ad67b74d24 ("printk: hash addresses printed with %p") the regular %p has been improved to avoid this issue. Furthermore, restricted pointers ("%pK") were never meant to be used through printk(). They can still unintentionally leak raw pointers or acquire sleeping locks in atomic contexts. Switch to the regular pointer formatting which is safer and easier to reason about. Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de> Reviewed-by: Amelie Delaunay <amelie.delaunay@foss.st.com> Link: https://lore.kernel.org/r/20250618-restricted-pointers-dma-v2-1-bc39dafc201d@linutronix.de Signed-off-by: Vinod Koul <vkoul@kernel.org>		2025-06-26 15:27:55 -07:00
..
Kconfig
Makefile
stm32-dma3.c	dmaengine: stm32: Don't use %pK through printk	2025-06-26 15:27:55 -07:00
stm32-dma.c	dmaengine: stm32: Don't use %pK through printk	2025-06-26 15:27:55 -07:00
stm32-dmamux.c
stm32-mdma.c	dmaengine: stm32: Don't use %pK through printk	2025-06-26 15:27:55 -07:00