From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Steven Rostedt <rostedt@goodmis.org>, Jiri Olsa <olsajiri@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
David Ahern <dsahern@kernel.org>,
Juri Lelli <juri.lelli@gmail.com>,
Breno Leitao <leitao@debian.org>,
netdev@vger.kernel.org,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>,
bpf@vger.kernel.org, Gabriele Monaco <gmonaco@redhat.com>
Subject: Re: [RFC][PATCH] tracepoint: Have tracepoints created with DECLARE_TRACE() have _tp suffix
Date: Mon, 21 Apr 2025 10:53:47 -0400 [thread overview]
Message-ID: <2730ae6d-b8e6-4464-b623-b1dd6a2e3110@efficios.com> (raw)
In-Reply-To: <20250421095817.49c433b7@gandalf.local.home>
On 2025-04-21 09:58, Steven Rostedt wrote:
> On Mon, 21 Apr 2025 14:44:21 +0200
> Jiri Olsa <olsajiri@gmail.com> wrote:
>
>> hi,
>> do we need the change also for DECLARE_TRACE_WRITABLE?
>
> Probably ;-)
>
>> I needed change below for bpf selftest kmod
>
> Thanks, I'll fold this in.
>
> I'll make a more formal patch if nobody has any objections.
No objection from me:
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thanks!
Mathieu
>
> -- Steve
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2025-04-21 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 15:01 [RFC][PATCH] tracepoint: Have tracepoints created with DECLARE_TRACE() have _tp suffix Steven Rostedt
2025-04-21 12:44 ` Jiri Olsa
2025-04-21 13:58 ` Steven Rostedt
2025-04-21 14:53 ` Mathieu Desnoyers [this message]
2025-04-23 18:21 ` Andrii Nakryiko
2025-04-23 18:53 ` Steven Rostedt
2025-04-23 21:21 ` Andrii Nakryiko
2025-04-23 21:27 ` 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=2730ae6d-b8e6-4464-b623-b1dd6a2e3110@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=dsahern@kernel.org \
--cc=gmonaco@redhat.com \
--cc=juri.lelli@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olsajiri@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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