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/4] tracing: A few more last minute updates for 4.13
Date: Mon, 10 Jul 2017 06:17:19 -0400 [thread overview]
Message-ID: <20170710101719.530502889@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: 8cb0bc9e3f863f3e77522d02443a75c0e45a6ed0
Masami Hiramatsu (1):
selftests/ftrace: Add a testcase for kprobe event naming
Naveen N. Rao (3):
trace/kprobes: Sanitize derived event names
selftests/ftrace: Update multiple kprobes test for powerpc
selftests/ftrace: Add a test to probe module functions
----
kernel/trace/trace_kprobe.c | 9 ++++++
.../ftrace/test.d/kprobe/kprobe_eventname.tc | 36 ++++++++++++++++++++++
.../ftrace/test.d/kprobe/kprobe_module.tc | 28 +++++++++++++++++
.../ftrace/test.d/kprobe/multiple_kprobes.tc | 4 +--
4 files changed, 75 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_eventname.tc
create mode 100644 tools/testing/selftests/ftrace/test.d/kprobe/kprobe_module.tc
next reply other threads:[~2017-07-10 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 10:17 Steven Rostedt [this message]
2017-07-10 10:17 ` [for-next][PATCH 1/4] trace/kprobes: Sanitize derived event names Steven Rostedt
2017-07-10 10:17 ` [for-next][PATCH 2/4] selftests/ftrace: Update multiple kprobes test for powerpc Steven Rostedt
2017-07-10 10:17 ` [for-next][PATCH 3/4] selftests/ftrace: Add a test to probe module functions Steven Rostedt
2017-07-10 10:17 ` [for-next][PATCH 4/4] selftests/ftrace: Add a testcase for kprobe event naming 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=20170710101719.530502889@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
Powered by JetHome