All of lore.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/3] tracing: Updates for 7.1
Date: Sun, 29 Mar 2026 11:55:12 -0400	[thread overview]
Message-ID: <20260329155512.926671150@kernel.org> (raw)

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

Head SHA1: e197453eb0c110d3d83fd1d2b324a93d5fcfa314


David Laight (1):
      tracing: Remove spurious default precision from show_event_trigger/filter formats

Steven Rostedt (1):
      tracing: Remove tracing_alloc_snapshot() when snapshot isn't defined

Vineeth Pillai (Google) (1):
      cpufreq: Use trace_call__##name() at guarded tracepoint call sites

----
 drivers/cpufreq/amd-pstate.c   | 10 +++++-----
 drivers/cpufreq/cpufreq.c      |  2 +-
 drivers/cpufreq/intel_pstate.c |  2 +-
 kernel/trace/trace.c           |  7 -------
 kernel/trace/trace_events.c    |  4 ++--
 5 files changed, 9 insertions(+), 16 deletions(-)

             reply	other threads:[~2026-03-29 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-29 15:55 Steven Rostedt [this message]
2026-03-29 15:55 ` [for-next][PATCH 1/3] tracing: Remove tracing_alloc_snapshot() when snapshot isnt defined Steven Rostedt
2026-03-29 15:55 ` [for-next][PATCH 2/3] cpufreq: Use trace_call__##name() at guarded tracepoint call sites Steven Rostedt
2026-03-29 15:55 ` [for-next][PATCH 3/3] tracing: Remove spurious default precision from show_event_trigger/filter formats 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=20260329155512.926671150@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 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.