From: Tree Davies <tdavies@darkphysics.net>
To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Tree Davies <tdavies@darkphysics.net>
Subject: [PATCH 1/5] Staging: rtl8192e: Rename variable pTS in function ResetRxTsEntry()
Date: Sat, 12 Aug 2023 23:54:41 -0700 [thread overview]
Message-ID: <20230813065445.95205-2-tdavies@darkphysics.net> (raw)
In-Reply-To: <20230813065445.95205-1-tdavies@darkphysics.net>
Rename variable pTS in function ResetRxTsEntry() to rx_ts
to fix checkpatch warning Avoid CamelCase.
Signed-off-by: Tree Davies <tdavies@darkphysics.net>
---
drivers/staging/rtl8192e/rtl819x_TSProc.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_TSProc.c b/drivers/staging/rtl8192e/rtl819x_TSProc.c
index 1c78134fc625..65521bd91b2e 100644
--- a/drivers/staging/rtl8192e/rtl819x_TSProc.c
+++ b/drivers/staging/rtl8192e/rtl819x_TSProc.c
@@ -113,12 +113,12 @@ static void ResetTxTsEntry(struct tx_ts_record *pTS)
rtllib_reset_ba_entry(&pTS->TxPendingBARecord);
}
-static void ResetRxTsEntry(struct rx_ts_record *pTS)
+static void ResetRxTsEntry(struct rx_ts_record *rx_ts)
{
- ResetTsCommonInfo(&pTS->ts_common_info);
- pTS->rx_indicate_seq = 0xffff;
- pTS->rx_timeout_indicate_seq = 0xffff;
- rtllib_reset_ba_entry(&pTS->rx_admitted_ba_record);
+ ResetTsCommonInfo(&rx_ts->ts_common_info);
+ rx_ts->rx_indicate_seq = 0xffff;
+ rx_ts->rx_timeout_indicate_seq = 0xffff;
+ rtllib_reset_ba_entry(&rx_ts->rx_admitted_ba_record);
}
void TSInitialize(struct rtllib_device *ieee)
--
2.41.0
next prev parent reply other threads:[~2023-08-13 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 6:54 [PATCH 0/5] Staging: rtl8192e: Series-B Rename struct rx_ts_record references Tree Davies
2023-08-13 6:54 ` Tree Davies [this message]
2023-08-13 6:54 ` [PATCH 2/5] Staging: rtl8192e: Rename variable pRxTS in function TSInitialize() Tree Davies
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=20230813065445.95205-2-tdavies@darkphysics.net \
--to=tdavies@darkphysics.net \
--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®