From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-doc@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>,
Namhyung Kim <namhyung@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Randy Dunlap <rdunlap@infradead.org>
Subject: [PATCH v2 0/2] tracing: Documentation: Add missing config and document for eprobes
Date: Tue, 29 Jul 2025 12:18:16 -0400 [thread overview]
Message-ID: <20250729161816.678462962@kernel.org> (raw)
Add missing eprobe config option and documentation which should have both been
added back in 5.15.
Steven Rostedt (2):
tracing: Have eprobes have their own config option
Documentation: tracing: Add documentation about eprobes
----
Documentation/trace/eprobetrace.rst | 269 ++++++++++++++++++++++++++++++++++++
Documentation/trace/index.rst | 1 +
kernel/trace/Kconfig | 13 ++
kernel/trace/Makefile | 2 +-
4 files changed, 284 insertions(+), 1 deletion(-)
create mode 100644 Documentation/trace/eprobetrace.rst
next reply other threads:[~2025-07-29 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-29 16:18 Steven Rostedt [this message]
2025-07-29 16:18 ` [PATCH v2 1/2] tracing: Have eprobes have their own config option Steven Rostedt
2025-07-30 3:07 ` Masami Hiramatsu
2025-07-30 6:27 ` kernel test robot
2025-07-30 10:11 ` Masami Hiramatsu
2025-07-30 13:17 ` Steven Rostedt
2025-07-30 13:57 ` Masami Hiramatsu
2025-07-30 14:01 ` Steven Rostedt
2025-07-30 22:08 ` Masami Hiramatsu
2025-07-31 11:43 ` Steven Rostedt
2025-07-29 16:18 ` [PATCH v2 2/2] Documentation: tracing: Add documentation about eprobes Steven Rostedt
2025-07-29 19:31 ` Randy Dunlap
2025-07-30 2:58 ` Masami Hiramatsu
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=20250729161816.678462962@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rdunlap@infradead.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.