linux-staging.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Artur Stupa <arthur.stupa@gmail.com>
To: gregkh@linuxfoundation.org
Cc: dan.carpenter@linaro.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Artur Stupa <arthur.stupa@gmail.com>
Subject: [PATCH v4 2/2] staging: rtl8723bs: core: delete commented-out code
Date: Fri, 21 Nov 2025 14:41:35 -0800	[thread overview]
Message-ID: <20251121224143.33701-2-arthur.stupa@gmail.com> (raw)
In-Reply-To: <20251121224143.33701-1-arthur.stupa@gmail.com>

Delete dead commented-out code.

No functional changes.

Signed-off-by: Artur Stupa <arthur.stupa@gmail.com>
---
Changes in v4:
* Documented changes between patch versions.

Changes in v3:
* Deleted dead commented-out code in rtw_sta_mgt.c.
* Moved dead commented-out code deletion here from patch 1/2.
---
 drivers/staging/rtl8723bs/core/rtw_sta_mgt.c   | 6 ------
 drivers/staging/rtl8723bs/core/rtw_wlan_util.c | 9 ---------
 2 files changed, 15 deletions(-)

diff --git a/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c b/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
index d1f6030799cb..3e80d03c4ec9 100644
--- a/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
+++ b/drivers/staging/rtl8723bs/core/rtw_sta_mgt.c
@@ -383,12 +383,6 @@ u32 rtw_free_stainfo(struct adapter *padapter, struct sta_info *psta)
 
 	/* release mac id for non-bc/mc station, */
 	rtw_release_macid(pstapriv->padapter, psta);
-
-/*
-	spin_lock_bh(&pstapriv->asoc_list_lock);
-	list_del_init(&psta->asoc_list);
-	spin_unlock_bh(&pstapriv->asoc_list_lock);
-*/
 	spin_lock_bh(&pstapriv->auth_list_lock);
 	if (!list_empty(&psta->auth_list)) {
 		list_del_init(&psta->auth_list);
diff --git a/drivers/staging/rtl8723bs/core/rtw_wlan_util.c b/drivers/staging/rtl8723bs/core/rtw_wlan_util.c
index c8909ffe0248..5ffefa50699e 100644
--- a/drivers/staging/rtl8723bs/core/rtw_wlan_util.c
+++ b/drivers/staging/rtl8723bs/core/rtw_wlan_util.c
@@ -1689,15 +1689,6 @@ void adaptive_early_32k(struct mlme_ext_priv *pmlmeext, u8 *pframe, uint len)
 	else
 		pmlmeext->bcn_delay_cnt[delay_ms]++;
 		/* pmlmeext->bcn_delay_ratio[delay_ms] = (pmlmeext->bcn_delay_cnt[delay_ms] * 100) /pmlmeext->bcn_cnt; */
-
-/*
-
-	for (i = 0; i<9; i++)
-	{
-			pmlmeext->bcn_delay_cnt[i] , i, pmlmeext->bcn_delay_ratio[i]);
-	}
-*/
-
 	/* dump for  adaptive_early_32k */
 	if (pmlmeext->bcn_cnt > 100 && (pmlmeext->adaptive_tsf_done == true)) {
 		u8 ratio_20_delay, ratio_80_delay;
-- 
2.43.0


  reply	other threads:[~2025-11-21 22:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  6:26 [PATCH] staging: rtl8723bs: core: fix block comment style issues Artur Stupa
2025-11-19 11:36 ` Dan Carpenter
2025-11-20  0:29 ` [PATCH v2] " Artur Stupa
2025-11-20  7:22   ` Dan Carpenter
2025-11-20 20:30   ` [PATCH v3 1/2] " Artur Stupa
2025-11-20 20:30     ` [PATCH v3 2/2] staging: rtl8723bs: core: delete commented-out code Artur Stupa
2025-11-21  6:59     ` [PATCH v3 1/2] staging: rtl8723bs: core: fix block comment style issues Greg KH
2025-11-21 22:41     ` [PATCH v4 " Artur Stupa
2025-11-21 22:41       ` Artur Stupa [this message]
2025-11-24  7:58       ` Dan Carpenter

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=20251121224143.33701-2-arthur.stupa@gmail.com \
    --to=arthur.stupa@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).