From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/3] tracing: Final updates for 6.3
Date: Fri, 17 Feb 2023 13:39:11 -0500 [thread overview]
Message-ID: <20230217183911.775065402@goodmis.org> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace.git
trace/for-next
Head SHA1: 2413ec4fd11248ef255f92fd12d943b49b6fbff4
Jianlin Lv (1):
tracepoint: Allow livepatch module add trace event
Ross Zwisler (1):
tracing: Always use canonical ftrace path
Wang ShaoBo (1):
tracing: Remove unnecessary NULL assignment
----
include/linux/kernel.h | 2 +-
include/linux/tracepoint.h | 4 ++--
kernel/trace/Kconfig | 20 ++++++++++----------
kernel/trace/kprobe_event_gen_test.c | 2 +-
kernel/trace/ring_buffer.c | 2 +-
kernel/trace/synth_event_gen_test.c | 2 +-
kernel/trace/trace.c | 2 +-
kernel/trace/trace_events.c | 2 --
kernel/tracepoint.c | 4 ++--
samples/user_events/example.c | 4 ++--
scripts/tracing/draw_functrace.py | 6 +++---
tools/lib/api/fs/tracing_path.c | 4 ++--
tools/tracing/latency/latency-collector.c | 2 +-
13 files changed, 27 insertions(+), 29 deletions(-)
next reply other threads:[~2023-02-17 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 18:39 Steven Rostedt [this message]
2023-02-17 18:39 ` [for-next][PATCH 1/3] tracing: Always use canonical ftrace path Steven Rostedt
2023-02-17 18:39 ` [for-next][PATCH 2/3] tracepoint: Allow livepatch module add trace event Steven Rostedt
2023-02-17 18:39 ` [for-next][PATCH 3/3] tracing: Remove unnecessary NULL assignment 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=20230217183911.775065402@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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