On Mon, 2013-03-18 at 09:34 +0100, Paul Bolle wrote: > The tracepoint sample code got removed. Remove a few lines on its usage > too. > > Acked-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx> > Acked-by: Rob Landley <rob@xxxxxxxxxxx> > Signed-off-by: Paul Bolle <pebolle@xxxxxxxxxx> > --- > Rob asked (off list) to submit this for the trivial tree. Sure, it can go that path. Acked-by: Steven Rostedt <rostedt@xxxxxxxxxxx> -- Steve > > Documentation/trace/tracepoints.txt | 15 --------------- > 1 file changed, 15 deletions(-) > > diff --git a/Documentation/trace/tracepoints.txt b/Documentation/trace/tracepoints.txt > index c0e1cee..da49437 100644 > --- a/Documentation/trace/tracepoints.txt > +++ b/Documentation/trace/tracepoints.txt > @@ -81,7 +81,6 @@ tracepoint_synchronize_unregister() must be called before the end of > the module exit function to make sure there is no caller left using > the probe. This, and the fact that preemption is disabled around the > probe call, make sure that probe removal and module unload are safe. > -See the "Probe example" section below for a sample probe module. > > The tracepoint mechanism supports inserting multiple instances of the > same tracepoint, but a single definition must be made of a given > @@ -100,17 +99,3 @@ core kernel image or in modules. > If the tracepoint has to be used in kernel modules, an > EXPORT_TRACEPOINT_SYMBOL_GPL() or EXPORT_TRACEPOINT_SYMBOL() can be > used to export the defined tracepoints. > - > -* Probe / tracepoint example > - > -See the example provided in samples/tracepoints > - > -Compile them with your kernel. They are built during 'make' (not > -'make modules') when CONFIG_SAMPLE_TRACEPOINTS=m. > - > -Run, as root : > -modprobe tracepoint-sample (insmod order is not important) > -modprobe tracepoint-probe-sample > -cat /proc/tracepoint-sample (returns an expected error) > -rmmod tracepoint-sample tracepoint-probe-sample > -dmesg -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
