From: Randy Dunlap <rdunlap@infradead.org>
To: Aaron Tomlin <atomlin@atomlin.com>,
rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com, corbet@lwn.net
Cc: neelx@suse.com, sean@ashe.io, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [v2 PATCH 2/2] tracing: Add show_event_triggers to expose active event triggers
Date: Mon, 5 Jan 2026 22:10:39 -0800 [thread overview]
Message-ID: <95feb439-2298-4539-8833-e05ed06f273b@infradead.org> (raw)
In-Reply-To: <20260105142939.2655342-3-atomlin@atomlin.com>
Hi,
On 1/5/26 6:29 AM, Aaron Tomlin wrote:
> diff --git a/Documentation/trace/ftrace.rst b/Documentation/trace/ftrace.rst
> index 4ce01e726b09..b9efb148a5c2 100644
> --- a/Documentation/trace/ftrace.rst
> +++ b/Documentation/trace/ftrace.rst
> @@ -692,6 +692,14 @@ of ftrace. Here is a list of some of the key files:
>
> See events.rst for more information.
>
> + show_event_triggers:
> +
> + A list of events that have triggers. This shows the
> + system/event pair along with the trigger that is attached to
> + the event.
> +
> + See events.rst for more information.
> +
Isn't this the same chunk that was in patch 1/2?
> available_events:
>
> A list of events that can be enabled in tracing.
--
~Randy
next prev parent reply other threads:[~2026-01-06 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 14:29 [v2 PATCH 0/2] tracing: Expose global views of active filters and triggers Aaron Tomlin
2026-01-05 14:29 ` [v2 PATCH 1/2] tracing: Add show_event_filters to expose active event filters Aaron Tomlin
2026-01-05 14:29 ` [v2 PATCH 2/2] tracing: Add show_event_triggers to expose active event triggers Aaron Tomlin
2026-01-06 6:10 ` Randy Dunlap [this message]
2026-01-06 15:17 ` Steven Rostedt
2026-01-06 16:08 ` Randy Dunlap
2026-01-07 1:15 ` Aaron Tomlin
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=95feb439-2298-4539-8833-e05ed06f273b@infradead.org \
--to=rdunlap@infradead.org \
--cc=atomlin@atomlin.com \
--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=neelx@suse.com \
--cc=rostedt@goodmis.org \
--cc=sean@ashe.io \
/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