From: Xingquan Liu <b1n@b1n.io>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Cc: Xingquan Liu <b1n@b1n.io>
Subject: [PATCH 1/7] staging: vt6655: Rename variable apCurrTD
Date: Sat, 21 Sep 2024 00:20:19 +0800 [thread overview]
Message-ID: <20240920162025.31465-1-b1n@b1n.io> (raw)
Rename variable apCurrTD to ap_curr_td to fix checkpatch warning
Avoid CamelCase.
Signed-off-by: Xingquan Liu <b1n@b1n.io>
---
drivers/staging/vt6655/card.c | 4 ++--
drivers/staging/vt6655/device.h | 2 +-
drivers/staging/vt6655/device_main.c | 8 ++++----
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/staging/vt6655/card.c b/drivers/staging/vt6655/card.c
index 6a2e390e9493..3b7284a23479 100644
--- a/drivers/staging/vt6655/card.c
+++ b/drivers/staging/vt6655/card.c
@@ -389,10 +389,10 @@ void card_safe_reset_tx(struct vnt_private *priv)
/* initialize TD index */
priv->tail_td[0] = &priv->ap_td0_rings[0];
- priv->apCurrTD[0] = &priv->ap_td0_rings[0];
+ priv->ap_curr_td[0] = &priv->ap_td0_rings[0];
priv->tail_td[1] = &priv->ap_td1_rings[0];
- priv->apCurrTD[1] = &priv->ap_td1_rings[0];
+ priv->ap_curr_td[1] = &priv->ap_td1_rings[0];
for (uu = 0; uu < TYPE_MAXTD; uu++)
priv->iTDUsed[uu] = 0;
diff --git a/drivers/staging/vt6655/device.h b/drivers/staging/vt6655/device.h
index 5eaab6b172d3..f4e14c65b1a8 100644
--- a/drivers/staging/vt6655/device.h
+++ b/drivers/staging/vt6655/device.h
@@ -132,7 +132,7 @@ struct vnt_private {
volatile int iTDUsed[TYPE_MAXTD];
- struct vnt_tx_desc *apCurrTD[TYPE_MAXTD];
+ struct vnt_tx_desc *ap_curr_td[TYPE_MAXTD];
struct vnt_tx_desc *tail_td[TYPE_MAXTD];
struct vnt_tx_desc *ap_td0_rings;
diff --git a/drivers/staging/vt6655/device_main.c b/drivers/staging/vt6655/device_main.c
index bf3ecf720206..052ebe0095a5 100644
--- a/drivers/staging/vt6655/device_main.c
+++ b/drivers/staging/vt6655/device_main.c
@@ -737,7 +737,7 @@ static int device_init_td0_ring(struct vnt_private *priv)
if (i > 0)
priv->ap_td0_rings[i - 1].next_desc = cpu_to_le32(priv->td0_pool_dma);
- priv->tail_td[0] = priv->apCurrTD[0] = &priv->ap_td0_rings[0];
+ priv->tail_td[0] = priv->ap_curr_td[0] = &priv->ap_td0_rings[0];
return 0;
@@ -777,7 +777,7 @@ static int device_init_td1_ring(struct vnt_private *priv)
if (i > 0)
priv->ap_td1_rings[i - 1].next_desc = cpu_to_le32(priv->td1_pool_dma);
- priv->tail_td[1] = priv->apCurrTD[1] = &priv->ap_td1_rings[0];
+ priv->tail_td[1] = priv->ap_curr_td[1] = &priv->ap_td1_rings[0];
return 0;
@@ -1235,7 +1235,7 @@ static int vnt_tx_packet(struct vnt_private *priv, struct sk_buff *skb)
return -ENOMEM;
}
- head_td = priv->apCurrTD[dma_idx];
+ head_td = priv->ap_curr_td[dma_idx];
head_td->td1.tcr = 0;
@@ -1244,7 +1244,7 @@ static int vnt_tx_packet(struct vnt_private *priv, struct sk_buff *skb)
if (dma_idx == TYPE_AC0DMA)
head_td->td_info->flags = TD_FLAGS_NETIF_SKB;
- priv->apCurrTD[dma_idx] = head_td->next;
+ priv->ap_curr_td[dma_idx] = head_td->next;
spin_unlock_irqrestore(&priv->lock, flags);
--
Xingquan Liu
next reply other threads:[~2024-09-20 16:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 16:20 Xingquan Liu [this message]
2024-09-20 16:20 ` [PATCH 2/7] staging: vt6655: Rename variable iTDUsed Xingquan Liu
2024-09-21 14:10 ` Philipp Hortmann
2024-09-22 4:46 ` Xingquan Liu
2024-09-23 12:09 ` Xingquan Liu
2024-09-24 7:29 ` Philipp Hortmann
2024-09-24 13:09 ` Xingquan Liu
2024-09-20 16:20 ` [PATCH 3/7] staging: vt6655: Rename function CARDvSafeResetRx Xingquan Liu
2024-09-20 16:20 ` [PATCH 4/7] staging: vt6655: Rename variable pDesc Xingquan Liu
2024-09-20 16:20 ` [PATCH 5/7] staging: vt6655: Rename variable pCurrRD Xingquan Liu
2024-09-20 16:20 ` [PATCH 6/7] staging: vt6655: Rename variable aRD0Ring Xingquan Liu
2024-09-20 16:20 ` [PATCH 7/7] staging: vt6655: Rename variable aRD1Ring Xingquan Liu
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=20240920162025.31465-1-b1n@b1n.io \
--to=b1n@b1n.io \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@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
all inboxes | Powered by JetHome®