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/6] tracing: Some last minute fixes for 5.6
Date: Sat, 01 Feb 2020 13:12:10 -0500 [thread overview]
Message-ID: <20200201181210.203806308@goodmis.org> (raw)
Tom Zanussi (6):
tracing: Change trace_boot to use synth_event interface
tracing: Fix now invalid var_ref_vals assumption in trace action
tracing: Consolidate some synth_event_trace code
tracing: Remove check_arg() callbacks from dynevent args
tracing: Remove useless code in dynevent_arg_pair_add()
tracing: Use seq_buf for building dynevent_cmd string
----
include/linux/trace_events.h | 4 +-
kernel/trace/trace_boot.c | 31 +++---
kernel/trace/trace_dynevent.c | 110 ++++++++-----------
kernel/trace/trace_dynevent.h | 11 +-
kernel/trace/trace_events_hist.c | 221 +++++++++++++++++++--------------------
kernel/trace/trace_kprobe.c | 12 +--
6 files changed, 171 insertions(+), 218 deletions(-)
next reply other threads:[~2020-02-01 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 18:12 Steven Rostedt [this message]
2020-02-01 18:12 ` [for-next][PATCH 1/6] tracing: Change trace_boot to use synth_event interface Steven Rostedt
2020-02-01 18:12 ` [for-next][PATCH 2/6] tracing: Fix now invalid var_ref_vals assumption in trace action Steven Rostedt
2020-02-01 18:12 ` [for-next][PATCH 3/6] tracing: Consolidate some synth_event_trace code Steven Rostedt
2020-02-01 18:12 ` [for-next][PATCH 4/6] tracing: Remove check_arg() callbacks from dynevent args Steven Rostedt
2020-02-01 18:12 ` [for-next][PATCH 5/6] tracing: Remove useless code in dynevent_arg_pair_add() Steven Rostedt
2020-02-01 18:12 ` [for-next][PATCH 6/6] tracing: Use seq_buf for building dynevent_cmd string 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=20200201181210.203806308@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