From: Dharanitharan R <dharanitharan725@gmail.com>
To: gregkh@linuxfoundation.org
Cc: trohan2000@gmail.com, bqn9090@gmail.com, straube.linux@gmail.com,
hansg@kernel.org, abrahamadekunle50@gmail.com,
davidzalman.101@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Dharanitharan R <dharanitharan725@gmail.com>
Subject: [PATCH] staging: rtl8723bs: Fix inconsistent indenting warning in rtw_ap.c
Date: Tue, 3 Feb 2026 01:43:16 +0000 [thread overview]
Message-ID: <20260203014315.23897-2-dharanitharan725@gmail.com> (raw)
Fix smatch/checkpatch reported inconsistent indenting warning
in rtw_ap.c.
drivers/staging/rtl8723bs/core/rtw_ap.c: fix inconsistent
indentation.
No functional changes were introduced.
Signed-off-by: Dharanitharan R <dharanitharan725@gmail.com>
---
drivers/staging/rtl8723bs/core/rtw_ap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_ap.c b/drivers/staging/rtl8723bs/core/rtw_ap.c
index 67197c7d4a4d..919bf8db6002 100644
--- a/drivers/staging/rtl8723bs/core/rtw_ap.c
+++ b/drivers/staging/rtl8723bs/core/rtw_ap.c
@@ -178,7 +178,6 @@ void expire_timeout_chk(struct adapter *padapter)
struct sta_priv *pstapriv = &padapter->stapriv;
u8 chk_alive_num = 0;
char chk_alive_list[NUM_STA];
- int i;
spin_lock_bh(&pstapriv->auth_list_lock);
@@ -278,7 +277,7 @@ void expire_timeout_chk(struct adapter *padapter)
}
/* issue null data to check sta alive*/
- for (i = 0; i < chk_alive_num; i++) {
+ for (int i = 0; i < chk_alive_num; i++) {
int ret = _FAIL;
psta = rtw_get_stainfo_by_offset(pstapriv, chk_alive_list[i]);
--
2.43.0
next reply other threads:[~2026-02-03 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 1:43 Dharanitharan R [this message]
2026-02-03 4:11 ` [PATCH] staging: rtl8723bs: Fix inconsistent indenting warning in rtw_ap.c Ethan Tidmore
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=20260203014315.23897-2-dharanitharan725@gmail.com \
--to=dharanitharan725@gmail.com \
--cc=abrahamadekunle50@gmail.com \
--cc=bqn9090@gmail.com \
--cc=davidzalman.101@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=straube.linux@gmail.com \
--cc=trohan2000@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