Skip to contentSkip to conversation

tracing: Remove stray tab in TRACE_EVAL_MAP_FILE's help text

PATCH New Borislav Petkov 1 participant 1 message Nov 12, 2019 Tracing

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 tracing: Remove stray tab in TRACE_EVAL_MAP_FILE's help text

From: Borislav Petkov <[email protected]>

There was a stray tab in the help text of the aforementioned config option which showed like this:

The "print fmt" of the trace events will show the enum/sizeof names
instead of their values. This can cause problems for user space tools
...

in menuconfig. Remove it and end a sentence with a fullstop.

No functional changes.

---
 kernel/trace/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/trace/Kconfig +2 -2
index e08527f50d2a..d201bf8ee3b7 100644
@@ -763,7 +763,7 @@ config TRACE_EVAL_MAP_FILE
        depends on TRACING
        help
 	The "print fmt" of the trace events will show the enum/sizeof names
-	instead	of their values. This can cause problems for user space tools
+	instead of their values. This can cause problems for user space tools
 	that use this string to parse the raw data as user space does not know
 	how to convert the string to its value.
 
@@ -784,7 +784,7 @@ config TRACE_EVAL_MAP_FILE
 	they are needed for the "eval_map" file. Enabling this option will
 	increase the memory footprint of the running kernel.
 
-	If unsure, say N
+	If unsure, say N.
 
 config GCOV_PROFILE_FTRACE
 	bool "Enable GCOV profiling on ftrace subsystem"
Signature · 1 line
2.21.0