summaryrefslogtreecommitdiff
path: root/scripts/Makefile.thinlto
diff options
context:
space:
mode:
authorEliav Farber <farbere@amazon.com>2026-10-11 05:04:42 +0000
committerThomas Gleixner <tglx@kernel.org>2026-10-15 14:25:06 +0200
commitda0b1e5f7a124c5c506baef32ed7a90aa03cf516 (patch)
tree05f10fe3a6bdea3ef52ce17797c5811cc2a92f07 /scripts/Makefile.thinlto
parente86459748d3119e18faee281408f5452865bfea4 (diff)
downloadlinux-da0b1e5f7a124c5c506baef32ed7a90aa03cf516.tar.gz
linux-da0b1e5f7a124c5c506baef32ed7a90aa03cf516.zip
irqchip/al-fic: Use %pOF and raise init log level
Use %pOF in the driver's log messages, so that both the success and the error paths identify the specific FIC instance by its full devicetree path rather than by its bare node name, e.g.: /soc/interrupt-controller@fd803000 initialized successfully in Legacy mode (parent-irq=3) A single controller is described by several FIC nodes that share the same bare node name (e.g. "interrupt-controller"), so the bare name cannot tell one instance from another. The full path includes the unit address and keeps the instances distinguishable. While converting the parent-missing message, fix a grammar typo in it ("device require a parent" -> "device requires a parent"). Raise the successful-initialization message from pr_debug to pr_info, as this single boot-time printout is useful when dynamic debug is not enabled at this stage of boot. Signed-off-by: Eliav Farber <farbere@amazon.com> Signed-off-by: Thomas Gleixner <tglx@kernel.org> Reviewed-by: Radu Rendec <radu@rendec.net> Link: https://patch.msgid.link/20261011050449.41903-4-farbere@amazon.com
Diffstat (limited to 'scripts/Makefile.thinlto')
0 files changed, 0 insertions, 0 deletions