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-linus][PATCH 0/5] tracing: Fixes for 6.1
Date: Wed, 12 Oct 2022 17:59:11 -0400 [thread overview]
Message-ID: <20221012215911.735621065@goodmis.org> (raw)
Jiapeng Chong (1):
ring-buffer: Fix kernel-doc
Steven Rostedt (Google) (3):
tracing: Move duplicate code of trace_kprobe/eprobe.c into header
tracing: Add "(fault)" name injection to kernel probes
tracing: Fix reading strings from synthetic events
Zheng Yejian (1):
ftrace: Fix char print issue in print_ip_ins()
----
kernel/trace/ftrace.c | 5 +-
kernel/trace/ring_buffer.c | 6 +-
kernel/trace/trace_eprobe.c | 60 ++------------------
kernel/trace/trace_events_synth.c | 23 ++++++--
kernel/trace/trace_kprobe.c | 60 ++------------------
kernel/trace/trace_probe_kernel.h | 115 ++++++++++++++++++++++++++++++++++++++
6 files changed, 146 insertions(+), 123 deletions(-)
create mode 100644 kernel/trace/trace_probe_kernel.h
next reply other threads:[~2022-10-12 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 21:59 Steven Rostedt [this message]
2022-10-12 21:59 ` [for-linus][PATCH 1/5] ftrace: Fix char print issue in print_ip_ins() Steven Rostedt
2022-10-12 21:59 ` [for-linus][PATCH 2/5] ring-buffer: Fix kernel-doc Steven Rostedt
2022-10-12 21:59 ` [for-linus][PATCH 3/5] tracing: Move duplicate code of trace_kprobe/eprobe.c into header Steven Rostedt
2022-10-12 21:59 ` [for-linus][PATCH 4/5] tracing: Add "(fault)" name injection to kernel probes Steven Rostedt
2022-10-12 21:59 ` [for-linus][PATCH 5/5] tracing: Fix reading strings from synthetic events 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=20221012215911.735621065@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