public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Colin Ian King <colin.i.king@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing/hist: add in missing * in comment blocks
Date: Thu, 20 Oct 2022 23:44:23 +0900	[thread overview]
Message-ID: <20221020234423.42816821e2d09aba61db5e69@kernel.org> (raw)
In-Reply-To: <20221020133019.1547587-1-colin.i.king@gmail.com>

Hi,

On Thu, 20 Oct 2022 14:30:19 +0100
Colin Ian King <colin.i.king@gmail.com> wrote:

> There are a couple of missing * in comment blocks. Fix these.
> Cleans up two clang warnings:
> 
> kernel/trace/trace_events_hist.c:986: warning: bad line:
> kernel/trace/trace_events_hist.c:3229: warning: bad line:
> 
> Signed-off-by: Colin Ian King <colin.i.king@gmail.com>

Thanks for the patch. 

Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>

BTW, what version of clang are you using?
I couldn't see this warning with clang 15.0.0. Maybe I need a kconfig option?

Thank you,

> ---
>  kernel/trace/trace_events_hist.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_hist.c b/kernel/trace/trace_events_hist.c
> index 48465f7e97b4..087c19548049 100644
> --- a/kernel/trace/trace_events_hist.c
> +++ b/kernel/trace/trace_events_hist.c
> @@ -983,7 +983,7 @@ static struct hist_field *find_any_var_ref(struct hist_trigger_data *hist_data,
>   * A trigger can define one or more variables.  If any one of them is
>   * currently referenced by any other trigger, this function will
>   * determine that.
> -
> + *
>   * Typically used to determine whether or not a trigger can be removed
>   * - if there are any references to a trigger's variables, it cannot.
>   *
> @@ -3226,7 +3226,7 @@ static struct field_var *create_field_var(struct hist_trigger_data *hist_data,
>   * events.  However, for convenience, users are allowed to directly
>   * specify an event field in an action, which will be automatically
>   * converted into a variable on their behalf.
> -
> + *
>   * This function creates a field variable with the name var_name on
>   * the hist trigger currently being defined on the target event.  If
>   * subsys_name and event_name are specified, this function simply
> -- 
> 2.37.3
> 


-- 
Masami Hiramatsu (Google) <mhiramat@kernel.org>

  reply	other threads:[~2022-10-20 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 13:30 [PATCH] tracing/hist: add in missing * in comment blocks Colin Ian King
2022-10-20 14:44 ` Masami Hiramatsu [this message]
2022-10-20 15:10   ` Colin King (gmail)
2022-10-20 18:07     ` Randy Dunlap
2022-10-21 14:28       ` Masami Hiramatsu

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=20221020234423.42816821e2d09aba61db5e69@kernel.org \
    --to=mhiramat@kernel.org \
    --cc=colin.i.king@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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