tracepoints: It is CONFIG_TRACEPOINTS not CONFIG_TRACEPOINT
authorLi zeming <zeming@nfschina.com>
Thu, 21 Jul 2022 08:19:04 +0000 (16:19 +0800)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Tue, 2 Aug 2022 19:15:56 +0000 (15:15 -0400)
When reading this note, CONFIG_TRACEPOINT searches my configuration
file, and the result is CONFIG_TRACEPOINTS, the search results are
consistent with the following macro definitions. I think it should be
repaired.

Link: https://lkml.kernel.org/r/20220721081904.3798-1-zeming@nfschina.com
Signed-off-by: Li zeming <zeming@nfschina.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
include/linux/tracepoint.h

index 28031b15f878380fafdc8040d1dabe710ec6b583..2908cc5ed70e1dcd8af0fa4ed7cb3871ce9336d1 100644 (file)
@@ -151,7 +151,7 @@ static inline struct tracepoint *tracepoint_ptr_deref(tracepoint_ptr_t *p)
 /*
  * Individual subsystem my have a separate configuration to
  * enable their tracepoints. By default, this file will create
- * the tracepoints if CONFIG_TRACEPOINT is defined. If a subsystem
+ * the tracepoints if CONFIG_TRACEPOINTS is defined. If a subsystem
  * wants to be able to disable its tracepoints from being created
  * it can define NOTRACE before including the tracepoint headers.
  */