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/2] tracing: Final updates for 7.0
Date: Tue, 10 Feb 2026 10:50:27 -0500 [thread overview]
Message-ID: <20260210155027.468969167@kernel.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: f743435f988cb0cf1f521035aee857851b25e06d
Colin Lord (1):
tracing: Fix false sharing in hwlat get_sample()
Steven Rostedt (1):
tracing: Move d_max_latency out of CONFIG_FSNOTIFY protection
----
kernel/trace/trace.h | 2 +-
kernel/trace/trace_hwlat.c | 15 +++++++--------
2 files changed, 8 insertions(+), 9 deletions(-)
next reply other threads:[~2026-02-10 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 15:50 Steven Rostedt [this message]
2026-02-10 15:50 ` [for-next][PATCH 1/2] tracing: Move d_max_latency out of CONFIG_FSNOTIFY protection Steven Rostedt
2026-02-10 15:50 ` [for-next][PATCH 2/2] tracing: Fix false sharing in hwlat get_sample() 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=20260210155027.468969167@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.