public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@kernel.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 0/4] tracing: Updates for v6.19
Date: Wed, 12 Nov 2025 10:22:35 -0500	[thread overview]
Message-ID: <20251112152235.655878322@kernel.org> (raw)

  git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next

Head SHA1: ecef4b5565a7653df68f2fee7cdcb174e561f0b3


Masami Hiramatsu (Google) (1):
      tracing: Report wrong dynamic event command

Steven Rostedt (3):
      tracing: Have tracer option be instance specific
      tracing: Have function tracer define options per instance
      tracing: Have function graph tracer define options per instance

----
 kernel/trace/trace.c                 | 257 +++++++++++++++++++++++++----------
 kernel/trace/trace.h                 |   3 +
 kernel/trace/trace_dynevent.c        |  11 +-
 kernel/trace/trace_functions.c       |  10 +-
 kernel/trace/trace_functions_graph.c |  18 ++-
 5 files changed, 211 insertions(+), 88 deletions(-)

             reply	other threads:[~2025-11-12 15:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-12 15:22 Steven Rostedt [this message]
2025-11-12 15:22 ` [for-next][PATCH 1/4] tracing: Report wrong dynamic event command Steven Rostedt
2025-11-12 15:22 ` [for-next][PATCH 2/4] tracing: Have tracer option be instance specific Steven Rostedt
2025-11-12 15:22 ` [for-next][PATCH 3/4] tracing: Have function tracer define options per instance Steven Rostedt
2025-11-12 15:22 ` [for-next][PATCH 4/4] tracing: Have function graph " 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=20251112152235.655878322@kernel.org \
    --to=rostedt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox