Skip to contentSkip to conversation

tracing/probes: fix typo in invalid variable error message

PATCH In review Yudistira Putra 2 participants 2 messages Jun 22 – Jun 23 Tracing

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tracing/probes: fix typo in invalid variable error message

Fix a typo in the BAD_VAR diagnostic emitted for invalid $-variables in probe event arguments.

---
 kernel/trace/trace_probe.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/trace_probe.h +1 -1
index 15758cc11fc6..0f09f7aaf93f 100644
@@ -511,7 +511,7 @@ extern int traceprobe_define_arg_fields(struct trace_event_call *event_call,
 	C(NO_RETVAL,		"This function returns 'void' type"),	\
 	C(BAD_STACK_NUM,	"Invalid stack number"),		\
 	C(BAD_ARG_NUM,		"Invalid argument number"),		\
-	C(BAD_VAR,		"Invalid $-valiable specified"),	\
+	C(BAD_VAR,		"Invalid $-variable specified"),	\
 	C(BAD_REG_NAME,		"Invalid register name"),		\
 	C(BAD_MEM_ADDR,		"Invalid memory address"),		\
 	C(BAD_IMM,		"Invalid immediate value"),		\
Signature · 1 line
2.43.0
#1 lore raw
Quoted 3 lines · On Mon, 22 Jun 2026 11:23:04 -0400 Yudistira Putra <[email protected]>…

Fix a typo in the BAD_VAR diagnostic emitted for invalid $-variables in probe event arguments.

Thanks, but the same fix are already picked.

https://lore.kernel.org/all/[email protected]/

Quoted 21 lines
---
 kernel/trace/trace_probe.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/trace_probe.h +1 -1
index 15758cc11fc6..0f09f7aaf93f 100644
@@ -511,7 +511,7 @@ extern int traceprobe_define_arg_fields(struct trace_event_call *event_call,
 	C(NO_RETVAL,		"This function returns 'void' type"),	\
 	C(BAD_STACK_NUM,	"Invalid stack number"),		\
 	C(BAD_ARG_NUM,		"Invalid argument number"),		\
-	C(BAD_VAR,		"Invalid $-valiable specified"),	\
+	C(BAD_VAR,		"Invalid $-variable specified"),	\
 	C(BAD_REG_NAME,		"Invalid register name"),		\
 	C(BAD_MEM_ADDR,		"Invalid memory address"),		\
 	C(BAD_IMM,		"Invalid immediate value"),		\
Signature · 1 line
2.43.0
Signature · 1 line
Masami Hiramatsu (Google) <[email protected]>