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 14:28:52 +0800 [thread overview]
Message-ID: <e0580876db3dbe6f9fedd2eb210bfe07@208suo.com> (raw)
In-Reply-To: <tencent_42BF9168164914C9431B82386C853B9EE609@qq.com>
Fixes the following checkpatch errors:
./drivers/net/ethernet/realtek/8139cp.c:1141: ERROR: space required
after that ',' (ctx:VxV)
./drivers/net/ethernet/realtek/8139cp.c:1152: ERROR: space required
after that ',' (ctx:VxV)
Signed-off-by: maqimei <2433033762@qq.com>
---
drivers/net/ethernet/realtek/8139cp.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/realtek/8139cp.c
b/drivers/net/ethernet/realtek/8139cp.c
index f5786d7..6c828b4 100644
--- a/drivers/net/ethernet/realtek/8139cp.c
+++ b/drivers/net/ethernet/realtek/8139cp.c
@@ -1138,7 +1138,7 @@ static void cp_clean_rings (struct cp_private *cp)
for (i = 0; i < CP_RX_RING_SIZE; i++) {
if (cp->rx_skb[i]) {
desc = cp->rx_ring + i;
- dma_unmap_single(&cp->pdev->dev,le64_to_cpu(desc->addr),
+ dma_unmap_single(&cp->pdev->dev, le64_to_cpu(desc->addr),
cp->rx_buf_sz, DMA_FROM_DEVICE);
dev_kfree_skb_any(cp->rx_skb[i]);
}
@@ -1149,7 +1149,7 @@ static void cp_clean_rings (struct cp_private *cp)
struct sk_buff *skb = cp->tx_skb[i];
desc = cp->tx_ring + i;
- dma_unmap_single(&cp->pdev->dev,le64_to_cpu(desc->addr),
+ dma_unmap_single(&cp->pdev->dev, le64_to_cpu(desc->addr),
le32_to_cpu(desc->opts1) & 0xffff,
DMA_TO_DEVICE);
if (le32_to_cpu(desc->opts1) & LastFrag)
next parent reply other threads:[~2023-07-17 6:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_42BF9168164914C9431B82386C853B9EE609@qq.com>
2023-07-17 6:28 ` hanyu001 [this message]
[not found] <tencent_86D2297E856205A9DAA674C8CD5B23912C0A@qq.com>
2023-07-17 1:59 ` [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=e0580876db3dbe6f9fedd2eb210bfe07@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.