From: Anirban Bose <boses156@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Anirban Bose <boses156@gmail.com>
Subject: [PATCH] staging: rtl8723bs: rename camelcase variable bDumpRxPkt
Date: Mon, 25 May 2026 12:29:35 +0530 [thread overview]
Message-ID: <20260525065935.130736-1-boses156@gmail.com> (raw)
Rename the local variable 'bDumpRxPkt' to 'dump_rx_pkt' in
validate_recv_frame() to resolve a checkpatch.pl CamelCase warning.
Signed-off-by: Anirban Bose <boses156@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_recv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c b/drivers/staging/rtl8723bs/core/rtw_recv.c
index 86c5e2c4e7dd..808f67b61f77 100644
--- a/drivers/staging/rtl8723bs/core/rtw_recv.c
+++ b/drivers/staging/rtl8723bs/core/rtw_recv.c
@@ -1447,7 +1447,7 @@ static signed int validate_recv_frame(struct adapter *adapter, union recv_frame
u8 type;
u8 subtype;
signed int retval = _SUCCESS;
- u8 bDumpRxPkt;
+ u8 dump_rx_pkt;
struct rx_pkt_attrib *pattrib = &precv_frame->u.hdr.attrib;
@@ -1473,7 +1473,7 @@ static signed int validate_recv_frame(struct adapter *adapter, union recv_frame
pattrib->mdata = GetMData(ptr);
pattrib->privacy = GetPrivacy(ptr);
pattrib->order = GetOrder(ptr);
- rtw_hal_get_def_var(adapter, HAL_DEF_DBG_DUMP_RXPKT, &(bDumpRxPkt));
+ rtw_hal_get_def_var(adapter, HAL_DEF_DBG_DUMP_RXPKT, &(dump_rx_pkt));
switch (type) {
case WIFI_MGT_TYPE: /* mgnt */
--
2.54.0
next reply other threads:[~2026-05-25 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-25 6:59 Anirban Bose [this message]
2026-07-07 10:17 ` [PATCH] staging: rtl8723bs: rename camelcase variable bDumpRxPkt Greg KH
2026-07-10 14:11 ` [PATCH v2] staging: rtl8723bs: remove unused " Anirban Bose
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=20260525065935.130736-1-boses156@gmail.com \
--to=boses156@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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.