From: hanyu001@208suo.com
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] drivers/net: space required after that ','
Date: Mon, 17 Jul 2023 09:59:27 +0800 [thread overview]
Message-ID: <9a2f9dac0bd4ec9a110ce66a1f26f6cd@208suo.com> (raw)
In-Reply-To: <tencent_86D2297E856205A9DAA674C8CD5B23912C0A@qq.com>
Fixes the following checkpatch errors:
./drivers/net/ethernet/myricom/myri10ge/myri10ge.c:354: ERROR: space
required after that ',' (ctx:VxV)
./drivers/net/ethernet/myricom/myri10ge/myri10ge.c:354: ERROR: space
required after that ',' (ctx:VxV)
./drivers/net/ethernet/myricom/myri10ge/myri10ge.c:354: ERROR: space
required after that ',' (ctx:VxV)
./drivers/net/ethernet/myricom/myri10ge/myri10ge.c:354: ERROR: space
required after that ',' (ctx:VxV)
Signed-off-by: maqimei <2433033762@qq.com>
---
drivers/net/ethernet/myricom/myri10ge/myri10ge.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
b/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
index c5687d9..65d7057 100644
--- a/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
+++ b/drivers/net/ethernet/myricom/myri10ge/myri10ge.c
@@ -351,7 +351,7 @@ struct myri10ge_priv {
(sizeof (X) == 8) ? ((u32)((u64)(X) >> 32)) : (0)
#define MYRI10GE_LOWPART_TO_U32(X) ((u32)(X))
-#define myri10ge_pio_copy(to,from,size)
__iowrite64_copy(to,from,size/8)
+#define myri10ge_pio_copy(to, from, size) __iowrite64_copy(to, from,
size/8)
static void myri10ge_set_multicast_list(struct net_device *dev);
static netdev_tx_t myri10ge_sw_tso(struct sk_buff *skb,
next parent reply other threads:[~2023-07-17 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_86D2297E856205A9DAA674C8CD5B23912C0A@qq.com>
2023-07-17 1:59 ` hanyu001 [this message]
[not found] <tencent_42BF9168164914C9431B82386C853B9EE609@qq.com>
2023-07-17 6:28 ` [PATCH] drivers/net: space required after that ',' hanyu001
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=9a2f9dac0bd4ec9a110ce66a1f26f6cd@208suo.com \
--to=hanyu001@208suo.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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