From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Lee, Chun-Yi" <jlee@suse.com>
Subject: [for-next][PATCH 02/19] tracepoints: Fix the descriptions of tracepoint_probe_register{_prio}
Date: Tue, 29 May 2018 11:23:06 -0400 [thread overview]
Message-ID: <20180529152326.148099543@goodmis.org> (raw)
In-Reply-To: <20180529152304.885389740@goodmis.org>
[-- Attachment #1: 0002-tracepoints-Fix-the-descriptions-of-tracepoint_probe.patch --]
[-- Type: text/plain, Size: 1232 bytes --]
From: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>
The description of tracepoint_probe_register duplicates
with tracepoint_probe_register_prio. This patch cleans up
the descriptions.
Link: http://lkml.kernel.org/r/20170616082643.7311-1-jlee@suse.com
Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
---
kernel/tracepoint.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/kernel/tracepoint.c b/kernel/tracepoint.c
index 1e37da2e0c25..6dc6356c3327 100644
--- a/kernel/tracepoint.c
+++ b/kernel/tracepoint.c
@@ -257,7 +257,7 @@ static int tracepoint_remove_func(struct tracepoint *tp,
}
/**
- * tracepoint_probe_register - Connect a probe to a tracepoint
+ * tracepoint_probe_register_prio - Connect a probe to a tracepoint with priority
* @tp: tracepoint
* @probe: probe handler
* @data: tracepoint data
@@ -290,7 +290,6 @@ EXPORT_SYMBOL_GPL(tracepoint_probe_register_prio);
* @tp: tracepoint
* @probe: probe handler
* @data: tracepoint data
- * @prio: priority of this function over other registered functions
*
* Returns 0 if ok, error value on error.
* Note: if @tp is within a module, the caller is responsible for
--
2.17.0
next prev parent reply other threads:[~2018-05-29 15:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-29 15:23 [for-next][PATCH 00/19] tracing: Updates for 4.18 Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 01/19] trace: Use -mcount-record for dynamic ftrace Steven Rostedt
2018-05-29 15:23 ` Steven Rostedt [this message]
2018-05-29 15:23 ` [for-next][PATCH 03/19] tracing: Do not reference event data in post call triggers Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 04/19] tracing: Add __find_event_file() to find event files without restrictions Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 05/19] tracing: Have event_trace_init() called by trace_init_tracefs() Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 06/19] tracing: Add brackets in ftrace event dynamic arrays Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 07/19] tracing: Do not show filter file for ftrace internal events Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 08/19] tracing: Add trigger file for trace_markers tracefs/ftrace/print Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 09/19] tracing: Have zero size length in filter logic be full string Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 10/19] tracing: Prevent further users of zero size static arrays in trace events Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 11/19] tracing: Allow histogram triggers to access ftrace internal events Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 12/19] tracing: Document trace_marker triggers Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 13/19] ftrace/selftest: Have the reset_trigger code be a bit more careful Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 14/19] ftrace/selftest: Fix reset_trigger() to handle triggers with filters Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 15/19] tracing/selftest: Add selftests to test trace_marker histogram triggers Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 16/19] tracing/selftest: Add test to test hist trigger between kernel event and trace_marker Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 17/19] tracing/selftest: Add test to test simple snapshot trigger for trace_marker Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 18/19] ring-buffer: Fix a bunch of typos in comments Steven Rostedt
2018-05-29 15:23 ` [for-next][PATCH 19/19] ring-buffer: Fix typo in comment 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=20180529152326.148099543@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=jlee@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®