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-linus][PATCH 0/5] tracing: Minor fixes for the last pull request
Date: Sun, 29 Sep 2019 16:06:42 -0400 [thread overview]
Message-ID: <20190929200642.036511084@goodmis.org> (raw)
Some final fix ups that will be sent to Linus shortly.
Changbin Du (1):
mm, tracing: Print symbol name for call_site in trace events
Masami Hiramatsu (1):
tracing/probe: Fix to check the difference of nr_args before adding probe
Nathan Chancellor (1):
tracing: Fix clang -Wint-in-bool-context warnings in IF_ASSIGN macro
Navid Emamdoost (1):
tracing: Have error path in predicate_parse() free its allocated memory
Steven Rostedt (VMware) (1):
selftests/ftrace: Fix same probe error test
----
include/trace/events/kmem.h | 7 ++++---
kernel/trace/trace.h | 10 +++++-----
kernel/trace/trace_events_filter.c | 6 ++++--
kernel/trace/trace_probe.c | 16 ++++++++++++++++
.../ftrace/test.d/kprobe/kprobe_syntax_errors.tc | 2 +-
5 files changed, 30 insertions(+), 11 deletions(-)
next reply other threads:[~2019-09-29 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 20:06 Steven Rostedt [this message]
2019-09-29 20:06 ` [for-linus][PATCH 1/5] tracing/probe: Fix to check the difference of nr_args before adding probe Steven Rostedt
2019-09-29 20:06 ` [for-linus][PATCH 2/5] tracing: Fix clang -Wint-in-bool-context warnings in IF_ASSIGN macro Steven Rostedt
2019-09-29 20:06 ` [for-linus][PATCH 3/5] tracing: Have error path in predicate_parse() free its allocated memory Steven Rostedt
2019-09-29 20:06 ` [for-linus][PATCH 4/5] mm, tracing: Print symbol name for call_site in trace events Steven Rostedt
2019-09-29 20:06 ` [for-linus][PATCH 5/5] selftests/ftrace: Fix same probe error test 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=20190929200642.036511084@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.