From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 00/13] tracing: More updates for 4.5.
Date: Thu, 24 Dec 2015 09:27:52 -0500 [thread overview]
Message-ID: <20151224142752.534947674@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 05a724bd44a68cd5c60bc4b949a946b57d4c9e55
Abel Vesa (1):
ftrace: Join functions ftrace_module_init() and ftrace_init_module()
Chuyu Hu (1):
tracing: Fix comment to use tracing_on over tracing_enable
Denis Kirjanov (1):
tracing: Introduce TRACE_EVENT_FN_COND macro
Jerry Snitselaar (1):
tracing: Use seq_buf_used() in seq_buf_to_user() instead of len
Julia Lawall (1):
bpf: Constify bpf_verifier_ops structure
Li Bin (4):
ftrace: Fix a typo in comment
ia64: ftrace: Fix the comments for ftrace_modify_code()
sh: ftrace: Fix the comments for ftrace_modify_code()
metag: ftrace: Fix the comments for ftrace_modify_code
Steven Rostedt (Red Hat) (4):
ftrace: Fix output of enabled_functions for showing tramp
ftrace: Remove use of control list and ops
ftrace: Have ftrace_ops_get_func() handle RCU and PER_CPU flags too
ftrace: Clean up ftrace_module_init() code
----
arch/ia64/kernel/ftrace.c | 12 ++-
arch/metag/kernel/ftrace.c | 11 ++-
arch/sh/kernel/ftrace.c | 12 ++-
include/linux/ftrace.h | 35 ++++----
include/linux/tracepoint.h | 4 +
include/trace/define_trace.h | 6 ++
include/trace/trace_events.h | 6 ++
kernel/trace/bpf_trace.c | 2 +-
kernel/trace/ftrace.c | 179 +++++++++++++++-------------------------
kernel/trace/trace.h | 6 +-
kernel/trace/trace_event_perf.c | 2 +-
lib/seq_buf.c | 6 +-
12 files changed, 122 insertions(+), 159 deletions(-)
next reply other threads:[~2015-12-24 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-24 14:27 Steven Rostedt [this message]
2015-12-24 14:27 ` [for-next][PATCH 01/13] ftrace: Fix a typo in comment Steven Rostedt
2015-12-24 14:27 ` [for-next][PATCH 02/13] ftrace: Fix output of enabled_functions for showing tramp Steven Rostedt
2015-12-24 14:27 ` [for-next][PATCH 03/13] ftrace: Remove use of control list and ops Steven Rostedt
2015-12-24 14:27 ` [for-next][PATCH 04/13] ftrace: Have ftrace_ops_get_func() handle RCU and PER_CPU flags too Steven Rostedt
2015-12-24 14:27 ` [for-next][PATCH 05/13] bpf: Constify bpf_verifier_ops structure Steven Rostedt
2015-12-24 14:27 ` [for-next][PATCH 06/13] tracing: Use seq_buf_used() in seq_buf_to_user() instead of len Steven Rostedt
2015-12-24 14:27 ` [for-next][PATCH 07/13] tracing: Introduce TRACE_EVENT_FN_COND macro Steven Rostedt
2015-12-24 14:28 ` [for-next][PATCH 08/13] ftrace: Join functions ftrace_module_init() and ftrace_init_module() Steven Rostedt
2015-12-24 14:28 ` [for-next][PATCH 09/13] ftrace: Clean up ftrace_module_init() code Steven Rostedt
2015-12-24 14:28 ` [for-next][PATCH 10/13] ia64: ftrace: Fix the comments for ftrace_modify_code() Steven Rostedt
2015-12-24 14:28 ` [for-next][PATCH 11/13] sh: " Steven Rostedt
2015-12-24 14:28 ` [for-next][PATCH 12/13] metag: ftrace: Fix the comments for ftrace_modify_code Steven Rostedt
2015-12-24 14:28 ` [for-next][PATCH 13/13] tracing: Fix comment to use tracing_on over tracing_enable 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=20151224142752.534947674@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--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