mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Rohit Visavalia <rohit.visavalia@softnautics.com>
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org, trivial@vger.kernel.org
Subject: Re: [PATCH] tracing: Block comments should align the * on each line
Date: Thu, 25 Jan 2018 12:05:52 -0500	[thread overview]
Message-ID: <20180125120552.408a0e67@vmware.local.home> (raw)
In-Reply-To: <20180125123136.12950-1-rohit.visavalia@softnautics.com>

On Thu, 25 Jan 2018 18:01:36 +0530
Rohit Visavalia <rohit.visavalia@softnautics.com> wrote:

> Resolved Block comments use * on subsequent lines checkpatch warning.
> Issue found by checkpatch.
>

This should go through the trivial tree.

Acked-by: Steven Rostedt (VMware) <rostedt@goodmis.org>

-- Steve
 
> Signed-off-by: Rohit Visavalia <rohit.visavalia@softnautics.com>
> ---
>  kernel/trace/trace.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 8e3f20a18a06..ad718932ff32 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -2380,7 +2380,7 @@ EXPORT_SYMBOL_GPL(trace_event_buffer_commit);
>   *   trace_buffer_unlock_commit_regs()
>   *   trace_event_buffer_commit()
>   *   trace_event_raw_event_xxx()
> -*/
> + */
>  # define STACK_SKIP 3
>  
>  void trace_buffer_unlock_commit_regs(struct trace_array *tr,

  reply	other threads:[~2018-01-25 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 12:31 Rohit Visavalia
2018-01-25 17:05 ` Steven Rostedt [this message]
2018-01-25 17:14   ` Steven Rostedt
     [not found]     ` <MA1PR0101MB1368478483A143904FCDA207F4E50@MA1PR0101MB1368.INDPRD01.PROD.OUTLOOK.COM>
     [not found]       ` <MA1PR0101MB1368F5EDED48FA0AA2501974F4E50@MA1PR0101MB1368.INDPRD01.PROD.OUTLOOK.COM>
2018-01-29  8:56         ` 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=20180125120552.408a0e67@vmware.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rohit.visavalia@softnautics.com \
    --cc=trivial@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®