From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: [for-next][PATCH 2/4] tracepoints: API doc update to data argument
Date: Wed, 19 Mar 2014 22:58:33 -0400 [thread overview]
Message-ID: <20140320030009.940568282@goodmis.org> (raw)
In-Reply-To: <20140320025831.285817697@goodmis.org>
[-- Attachment #1: 0001-tracepoints-API-doc-update-to-data-argument.patch --]
[-- Type: text/plain, Size: 2117 bytes --]
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Describe the @data argument (probe private data).
Link: http://lkml.kernel.org/r/1394587948-27878-1-git-send-email-mathieu.desnoyers@efficios.com
Fixes: 38516ab59fbc "tracing: Let tracepoints have data passed to tracepoint callbacks"
CC: Ingo Molnar <mingo@kernel.org>
CC: Frederic Weisbecker <fweisbec@gmail.com>
CC: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
---
kernel/tracepoint.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
index 0058f33..a4f629d 100644
--- a/kernel/tracepoint.c
+++ b/kernel/tracepoint.c
@@ -376,6 +376,7 @@ tracepoint_add_probe(const char *name, void *probe, void *data)
* tracepoint_probe_register - Connect a probe to a tracepoint
* @name: tracepoint name
* @probe: probe handler
+ * @data: probe private data
*
* Returns 0 if ok, error value on error.
* The probe address must at least be aligned on the architecture pointer size.
@@ -424,6 +425,7 @@ tracepoint_remove_probe(const char *name, void *probe, void *data)
* tracepoint_probe_unregister - Disconnect a probe from a tracepoint
* @name: tracepoint name
* @probe: probe function pointer
+ * @data: probe private data
*
* We do not need to call a synchronize_sched to make sure the probes have
* finished running before doing a module unload, because the module unload
@@ -464,6 +466,7 @@ static void tracepoint_add_old_probes(void *old)
* tracepoint_probe_register_noupdate - register a probe but not connect
* @name: tracepoint name
* @probe: probe handler
+ * @data: probe private data
*
* caller must call tracepoint_probe_update_all()
*/
@@ -488,6 +491,7 @@ EXPORT_SYMBOL_GPL(tracepoint_probe_register_noupdate);
* tracepoint_probe_unregister_noupdate - remove a probe but not disconnect
* @name: tracepoint name
* @probe: probe function pointer
+ * @data: probe private data
*
* caller must call tracepoint_probe_update_all()
*/
--
1.8.5.3
next prev parent reply other threads:[~2014-03-20 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 2:58 [for-next][PATCH 0/4] tracing: More updates for 3.15 Steven Rostedt
2014-03-20 2:58 ` [for-next][PATCH 1/4] ftrace: Fix compilation warning about control_ops_free Steven Rostedt
2014-03-20 2:58 ` Steven Rostedt [this message]
2014-03-20 2:58 ` [for-next][PATCH 3/4] tracepoints: API doc update to tracepoint_probe_register() return value Steven Rostedt
2014-03-20 2:58 ` [for-next][PATCH 4/4] ftrace: Constify ftrace_text_reserved Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140320030009.940568282@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome