From: Steven Rostedt <rostedt@goodmis.org>
To: MarileneGarcia <marilene.agarcia@gmail.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: adding the missing parameter descriptions of unregister_ftrace_direct
Date: Wed, 5 Jun 2024 22:09:45 -0400 [thread overview]
Message-ID: <20240605220945.63178ce1@gandalf.local.home> (raw)
In-Reply-To: <20240528005046.3778431-1-marilene.agarcia@gmail.com>
On Mon, 27 May 2024 21:50:46 -0300
MarileneGarcia <marilene.agarcia@gmail.com> wrote:
The subject for the tracing subsystem should start with a capital letter,
but it is a bit confusing anyway. Should be:
ftrace: Add missing kerneldoc parameters to unregister_ftrace_direct()
> Adding the description of the parameters addr and free_filters
> of the function unregister_ftrace_direct.
s/Adding/Add/ s/of the/to the/
>
> Signed-off-by: MarileneGarcia <marilene.agarcia@gmail.com>
> ---
> Hello,
> These changes fix the following compiler warnings of the function
> unregister_ftrace_direct.
>
> The warnings happen using GCC compiler, enabling the ftrace related
> configs and using the command 'make W=1'.
>
> kernel/trace/ftrace.c:5489: warning: Function parameter or struct member
> 'addr' not described in 'unregister_ftrace_direct'
>
> kernel/trace/ftrace.c:5489: warning: Function parameter or struct member
> 'free_filters' not described in 'unregister_ftrace_direct'
>
> kernel/trace/ftrace.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/trace/ftrace.c b/kernel/trace/ftrace.c
> index 65208d3b5ed9..6062e4ce1957 100644
> --- a/kernel/trace/ftrace.c
> +++ b/kernel/trace/ftrace.c
> @@ -5475,6 +5475,8 @@ EXPORT_SYMBOL_GPL(register_ftrace_direct);
> * unregister_ftrace_direct - Remove calls to custom trampoline
> * previously registered by register_ftrace_direct for @ops object.
> * @ops: The address of the struct ftrace_ops object
> + * @addr: The address of the trampoline to call at @ops functions
This is the unregister function. The above sounds like it will be called
instead of no longer being called.
@addr: The address of the direct function that are called by the @ops functions
> + * @free_filters: non zero to remove all filters for the ftrace_ops
It's a boolean value, there is no zero.
> *
> * This is used to remove a direct calls to @addr from the nop locations
> * of the functions registered in @ops (with by ftrace_set_filter_ip
-- Steve
prev parent reply other threads:[~2024-06-06 2:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 0:50 [PATCH] ftrace: adding the missing parameter descriptions of unregister_ftrace_direct MarileneGarcia
2024-06-04 23:23 ` Marilene Andrade Garcia
2024-06-06 2:09 ` Steven Rostedt [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=20240605220945.63178ce1@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=marilene.agarcia@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=skhan@linuxfoundation.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