From: Steven Rostedt <rostedt@goodmis.org>
To: sunran001@208suo.com
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] include: events: remove spaces after '(' and before ')'
Date: Sun, 23 Jul 2023 11:12:58 -0400 [thread overview]
Message-ID: <20230723111258.4e72787a@gandalf.local.home> (raw)
In-Reply-To: <7d6b48368594b2f815dff7c5375be638@208suo.com>
On Wed, 19 Jul 2023 11:21:03 +0800
sunran001@208suo.com wrote:
> Fix four occurrences of the checkpatch error:
>
> ERROR: space prohibited after that open parenthesis '('
> ERROR: space prohibited before that close parenthesis ')'
>
> Signed-off-by: Ran Sun <sunran001@208suo.com>
> ---
> include/trace/events/nmi.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/trace/events/nmi.h b/include/trace/events/nmi.h
> index 18e0411398ba..99abd0bc8ebd 100644
> --- a/include/trace/events/nmi.h
> +++ b/include/trace/events/nmi.h
> @@ -15,9 +15,9 @@ TRACE_EVENT(nmi_handler,
> TP_ARGS(handler, delta_ns, handled),
>
> TP_STRUCT__entry(
> - __field( void *, handler )
> - __field( s64, delta_ns)
> - __field( int, handled )
> + __field(void *, handler)
> + __field(s64, delta_ns)
> + __field(int, handled)
NACK!
Which version looks better?
checkpatch.pl fails horribly on TRACE_EVENT macros. DON'T MODIFY THEM!
-- Steve
> ),
>
> TP_fast_assign(
prev parent reply other threads:[~2023-07-23 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230719030939.18448-1-xujianghui@cdjrlc.com>
2023-07-19 3:21 ` [PATCH] include: events: remove spaces after '(' and before ')' sunran001
2023-07-23 15:12 ` 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=20230723111258.4e72787a@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=sunran001@208suo.com \
/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