From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 00/10] tracing: Updates for 6.15
Date: Sun, 23 Mar 2025 08:29:33 -0400 [thread overview]
Message-ID: <20250323122933.407277911@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: 25a5153c91ad23effc44dd349bea749f30208d45
Christophe JAILLET (1):
tracing: Constify struct event_trigger_ops
Douglas Raillard (3):
tracing: Align synth event print fmt
tracing: Ensure module defining synth event cannot be unloaded while tracing
tracing: Fix synth event printk format for str fields
Gabriele Paoloni (1):
tracing: fix return value in __ftrace_event_enable_disable for TRACE_REG_UNREGISTER
Huang Shijie (1):
tracepoint: Print the function symbol when tracepoint_debug is set
Petr Mladek (1):
tracing: gfp: vsprintf: Do not print "none" when using %pGg printf format
Ran Xiaokai (1):
tracing/osnoise: Fix possible recursive locking for cpus_read_lock()
Sasha Levin (1):
tracing: Use hashtable.h for event_hash
Steven Rostedt (1):
scripts/tracing: Remove scripts/tracing/draw_functrace.py
----
include/trace/events/mmflags.h | 2 +-
kernel/trace/trace.h | 4 +-
kernel/trace/trace_eprobe.c | 6 +-
kernel/trace/trace_events.c | 4 +-
kernel/trace/trace_events_hist.c | 20 +++---
kernel/trace/trace_events_synth.c | 35 +++++++++-
kernel/trace/trace_events_trigger.c | 38 +++++------
kernel/trace/trace_osnoise.c | 1 -
kernel/trace/trace_output.c | 19 ++----
kernel/tracepoint.c | 2 +-
scripts/tracing/draw_functrace.py | 129 ------------------------------------
11 files changed, 78 insertions(+), 182 deletions(-)
delete mode 100755 scripts/tracing/draw_functrace.py
next reply other threads:[~2025-03-23 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 12:29 Steven Rostedt [this message]
2025-03-23 12:29 ` [for-next][PATCH 01/10] scripts/tracing: Remove scripts/tracing/draw_functrace.py Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 02/10] tracing: Constify struct event_trigger_ops Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 03/10] tracepoint: Print the function symbol when tracepoint_debug is set Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 04/10] tracing: gfp: vsprintf: Do not print "none" when using %pGg printf format Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 05/10] tracing: Use hashtable.h for event_hash Steven Rostedt
2025-03-23 12:39 ` Steven Rostedt
2025-03-23 13:28 ` [PATCH] " Sasha Levin
2025-03-23 12:29 ` [for-next][PATCH 06/10] tracing: Align synth event print fmt Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 07/10] tracing/osnoise: Fix possible recursive locking for cpus_read_lock() Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 08/10] tracing: fix return value in __ftrace_event_enable_disable for TRACE_REG_UNREGISTER Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 09/10] tracing: Ensure module defining synth event cannot be unloaded while tracing Steven Rostedt
2025-03-23 12:29 ` [for-next][PATCH 10/10] tracing: Fix synth event printk format for str fields 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=20250323122933.407277911@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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.