|author||Steven Rostedt <email@example.com>||2013-01-25 09:46:36 -0500|
|committer||Steven Rostedt <firstname.lastname@example.org>||2013-01-25 11:22:11 -0500|
tracing: Remove tracepoint sample code
The tracepoint sample code was used to teach developers how to create their own tracepoints. But now the trace_events have been added as a higher level that is used directly by developers today. Only the trace_event code should use the tracepoint interface directly and no new tracepoints should be added. Besides, the example had a race condition with the use of the ->d_name.name dentry field, as pointed out by Al Viro. Best just to remove the code so it wont be used by other developers. Link: http://lkml.kernel.org/r/20130123225523.GY4939@ZenIV.linux.org.uk Cc: Al Viro <viro@ZenIV.linux.org.uk> Acked-by: Mathieu Desnoyers <email@example.com> Signed-off-by: Steven Rostedt <firstname.lastname@example.org>
Diffstat (limited to 'samples/Kconfig')
1 files changed, 0 insertions, 6 deletions
diff --git a/samples/Kconfig b/samples/Kconfig
index 7b6792a18c05..6181c2cc9ca0 100644
@@ -5,12 +5,6 @@ menuconfig SAMPLES
- tristate "Build tracepoints examples -- loadable modules only"
- depends on TRACEPOINTS && m
- This build tracepoints example modules.
tristate "Build trace_events examples -- loadable modules only"
depends on EVENT_TRACING && m