From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Mukesh Ojha <quic_mojha@quicinc.com>
Cc: Yujie Liu <yujie.liu@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Tom Zanussi <zanussi@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-trace-kernel@vger.kernel.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] tracing/kprobes: Fix the description of variable length arguments
Date: Fri, 27 Oct 2023 22:18:33 +0900 [thread overview]
Message-ID: <20231027221833.5f2c6d46dfd51110aafe6f58@kernel.org> (raw)
In-Reply-To: <aa71f7e3-71c5-1d2f-bc73-6db977025b41@quicinc.com>
On Fri, 27 Oct 2023 14:10:44 +0530
Mukesh Ojha <quic_mojha@quicinc.com> wrote:
>
>
> On 10/27/2023 9:43 AM, Yujie Liu wrote:
> > Fix the following kernel-doc warnings:
> >
> > kernel/trace/trace_kprobe.c:1029: warning: Excess function parameter 'args' description in '__kprobe_event_gen_cmd_start'
> > kernel/trace/trace_kprobe.c:1097: warning: Excess function parameter 'args' description in '__kprobe_event_add_fields'
> >
> > Refer to the usage of variable length arguments elsewhere in the kernel
> > code, "@..." is the proper way to express it in the description.
> >
> > Fixes: 2a588dd1d5d6 ("tracing: Add kprobe event command generation functions")
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202310190437.paI6LYJF-lkp@intel.com/
> > Signed-off-by: Yujie Liu <yujie.liu@intel.com>
>
> Not related to this patch, but I see order of the argument as well is
> not proper in the document of the __kprobe_event_gen_cmd_start(),
> if you can fix that too.
>
> LGTM, Thanks for this.
> Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
Thanks! let me pick this!
>
> -Mukesh
>
> > ---
> > kernel/trace/trace_kprobe.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/trace/trace_kprobe.c b/kernel/trace/trace_kprobe.c
> > index a8fef6ab0872..95c5b0668cb7 100644
> > --- a/kernel/trace/trace_kprobe.c
> > +++ b/kernel/trace/trace_kprobe.c
> > @@ -1007,7 +1007,7 @@ EXPORT_SYMBOL_GPL(kprobe_event_cmd_init);
> > * @name: The name of the kprobe event
> > * @loc: The location of the kprobe event
> > * @kretprobe: Is this a return probe?
> > - * @args: Variable number of arg (pairs), one pair for each field
> > + * @...: Variable number of arg (pairs), one pair for each field
> > *
> > * NOTE: Users normally won't want to call this function directly, but
> > * rather use the kprobe_event_gen_cmd_start() wrapper, which automatically
> > @@ -1080,7 +1080,7 @@ EXPORT_SYMBOL_GPL(__kprobe_event_gen_cmd_start);
> > /**
> > * __kprobe_event_add_fields - Add probe fields to a kprobe command from arg list
> > * @cmd: A pointer to the dynevent_cmd struct representing the new event
> > - * @args: Variable number of arg (pairs), one pair for each field
> > + * @...: Variable number of arg (pairs), one pair for each field
> > *
> > * NOTE: Users normally won't want to call this function directly, but
> > * rather use the kprobe_event_add_fields() wrapper, which
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2023-10-27 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 4:13 [PATCH] tracing/kprobes: Fix the description of variable length arguments Yujie Liu
2023-10-27 8:40 ` Mukesh Ojha
2023-10-27 13:18 ` 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=20231027221833.5f2c6d46dfd51110aafe6f58@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=quic_mojha@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=yujie.liu@intel.com \
--cc=zanussi@kernel.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.