From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Date: Fri, 14 Nov 2008 22:47:49 +0000 (-0500)
Subject: tracepoints, docs: marker_synchronize_unregister->tracepoint_synchronize_unregister
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=0dcf8fe5fe5d7279f1c479fa82f1f1ca6f22e814;p=GitHub%2Fmt8127%2Fandroid_kernel_alcatel_ttab.git

tracepoints, docs: marker_synchronize_unregister->tracepoint_synchronize_unregister

Impact: documentation update.

Signed-off-by: Zhaolei <zhaolei@cn.fujitsu.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---

diff --git a/Documentation/tracepoints.txt b/Documentation/tracepoints.txt
index 93cd90e89cc1..3a1c74384ffb 100644
--- a/Documentation/tracepoints.txt
+++ b/Documentation/tracepoints.txt
@@ -71,7 +71,7 @@ Connecting a function (probe) to a tracepoint is done by providing a probe
 (function to call) for the specific tracepoint through
 register_trace_subsys_eventname().  Removing a probe is done through
 unregister_trace_subsys_eventname(); it will remove the probe.
-marker_synchronize_unregister() must be called before the end of the module exit
+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