From: hanyu001@208suo.com
To: mpe@ellerman.id.au, npiggin@gmail.com, christophe.leroy@csgroup.eu
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH] powernv: vas-trace: remove space after '('
Date: Thu, 20 Jul 2023 15:05:50 +0800 [thread overview]
Message-ID: <28bb80fbf964a6c110b17ae1908e68de@208suo.com> (raw)
In-Reply-To: <tencent_17F68D4711DDD23ED72A9E0708C4549F540A@qq.com>
Fix below checkpatch errors:
/platforms/powernv/vas-trace.h:ERROR:space prohibited after that open
parenthesis '('
/platforms/powernv/vas-trace.h:ERROR:space prohibited after that open
parenthesis '('
/platforms/powernv/vas-trace.h:ERROR:space prohibited after that open
parenthesis '('
Signed-off-by: Yu Han <hanyu001@208suo.com>
---
arch/powerpc/platforms/powernv/vas-trace.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/vas-trace.h
b/arch/powerpc/platforms/powernv/vas-trace.h
index ca2e08f2ddc0..64acc0dccca8 100644
--- a/arch/powerpc/platforms/powernv/vas-trace.h
+++ b/arch/powerpc/platforms/powernv/vas-trace.h
@@ -10,7 +10,7 @@
#include <linux/sched.h>
#include <asm/vas.h>
-TRACE_EVENT( vas_rx_win_open,
+TRACE_EVENT(vas_rx_win_open,
TP_PROTO(struct task_struct *tsk,
int vasid,
@@ -45,7 +45,7 @@ TRACE_EVENT( vas_rx_win_open,
__entry->lnotify_tid)
);
-TRACE_EVENT( vas_tx_win_open,
+TRACE_EVENT(vas_tx_win_open,
TP_PROTO(struct task_struct *tsk,
int vasid,
@@ -77,7 +77,7 @@ TRACE_EVENT( vas_tx_win_open,
__entry->lpid, __entry->pidr)
);
-TRACE_EVENT( vas_paste_crb,
+TRACE_EVENT(vas_paste_crb,
TP_PROTO(struct task_struct *tsk,
struct pnv_vas_window *win),
parent reply other threads:[~2023-07-20 7:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_17F68D4711DDD23ED72A9E0708C4549F540A@qq.com>]
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=28bb80fbf964a6c110b17ae1908e68de@208suo.com \
--to=hanyu001@208suo.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).