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 0/5] tracing: function graph cleanups for the next merge window
Date: Thu, 25 Apr 2019 12:28:08 -0400 [thread overview]
Message-ID: <20190425162808.056301033@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 070ea1a24f403b68e76d9763cedd061917f6e1c1
Steven Rostedt (VMware) (5):
ftrace: Remove ASSIGN_OPS_HASH() macro from ftrace.c
ftrace: Do not process STUB functions in ftrace_ops_list_func()
function_graph: Have selftest also emulate tr->reset() as it did with tr->init()
function_graph: Use a ftrace_graph_ret_stub() for return
function_graph: Place ftrace_graph_entry_stub() prototype in include/linux/ftrace.h
----
arch/nds32/kernel/ftrace.c | 1 -
arch/parisc/kernel/ftrace.c | 1 -
include/linux/ftrace.h | 2 ++
kernel/trace/fgraph.c | 9 ++++++---
kernel/trace/ftrace.c | 7 +++----
kernel/trace/trace_selftest.c | 5 ++++-
6 files changed, 15 insertions(+), 10 deletions(-)
next reply other threads:[~2019-04-25 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 16:28 Steven Rostedt [this message]
2019-04-25 16:28 ` [for-next][PATCH 1/5] ftrace: Remove ASSIGN_OPS_HASH() macro from ftrace.c Steven Rostedt
2019-04-25 16:28 ` [for-next][PATCH 2/5] ftrace: Do not process STUB functions in ftrace_ops_list_func() Steven Rostedt
2019-04-25 16:28 ` [for-next][PATCH 3/5] function_graph: Have selftest also emulate tr->reset() as it did with tr->init() Steven Rostedt
2019-04-25 16:28 ` [for-next][PATCH 4/5] function_graph: Use a ftrace_graph_ret_stub() for return Steven Rostedt
2019-04-25 16:28 ` [for-next][PATCH 5/5] function_graph: Place ftrace_graph_entry_stub() prototype in include/linux/ftrace.h 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=20190425162808.056301033@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.