From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] tracing: trace_fprobe: fix typo in function name
Date: Fri, 19 Jun 2026 08:43:51 +0900 [thread overview]
Message-ID: <20260619084351.5aa9ca3be9d0e9deb971f10a@kernel.org> (raw)
In-Reply-To: <20260507081041.885781-5-martin@kaiser.cx>
On Thu, 7 May 2026 10:09:09 +0200
Martin Kaiser <martin@kaiser.cx> wrote:
> The function name should be __register_tracepoint_fprobe.
>
This looks good to me. Let me pick it.
Thanks,
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> ---
> kernel/trace/trace_fprobe.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/trace/trace_fprobe.c b/kernel/trace/trace_fprobe.c
> index 9f5f08c0e7c2..4d1abbf66229 100644
> --- a/kernel/trace/trace_fprobe.c
> +++ b/kernel/trace/trace_fprobe.c
> @@ -764,7 +764,7 @@ static int unregister_fprobe_event(struct trace_fprobe *tf)
> return trace_probe_unregister_event_call(&tf->tp);
> }
>
> -static int __regsiter_tracepoint_fprobe(struct trace_fprobe *tf)
> +static int __register_tracepoint_fprobe(struct trace_fprobe *tf)
> {
> struct tracepoint_user *tuser __free(tuser_put) = NULL;
> struct module *mod __free(module_put) = NULL;
> @@ -836,7 +836,7 @@ static int __register_trace_fprobe(struct trace_fprobe *tf)
> tf->fp.flags &= ~FPROBE_FL_DISABLED;
>
> if (trace_fprobe_is_tracepoint(tf))
> - return __regsiter_tracepoint_fprobe(tf);
> + return __register_tracepoint_fprobe(tf);
>
> /* TODO: handle filter, nofilter or symbol list */
> return register_fprobe(&tf->fp, tf->symbol, NULL);
> --
> 2.43.7
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2026-06-18 23:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 8:09 [PATCH 0/4] trace: trivial: fix some typos Martin Kaiser
2026-05-07 8:09 ` [PATCH 1/4] eventfs/tracing: fix typo in a comment Martin Kaiser
2026-05-07 8:09 ` [PATCH 2/4] perf/core: " Martin Kaiser
2026-05-07 8:09 ` [PATCH 3/4] tracing: probes: fix typo in a log message Martin Kaiser
2026-06-18 23:43 ` Masami Hiramatsu
2026-05-07 8:09 ` [PATCH 4/4] tracing: trace_fprobe: fix typo in function name Martin Kaiser
2026-06-18 23:43 ` Masami Hiramatsu [this message]
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=20260619084351.5aa9ca3be9d0e9deb971f10a@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=martin@kaiser.cx \
--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