public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ethan Tidmore <ethantidmore06@gmail.com>
To: gregkh@linuxfoundation.org
Cc: dan.carpenter@linaro.org, straube.linux@gmail.com,
	hansg@kernel.org, linux-staging@lists.linux.dev,
	linux-kernel@vger.kernel.org,
	Ethan Tidmore <ethantidmore06@gmail.com>
Subject: [PATCH v2 8/8] staging: rtl8723bs: remove unused variable RFE_Type
Date: Mon, 26 Jan 2026 19:21:18 -0600	[thread overview]
Message-ID: <20260127012118.43037-9-ethantidmore06@gmail.com> (raw)
In-Reply-To: <20260127012118.43037-1-ethantidmore06@gmail.com>

The variable RFE_Type is initialized but never read or used
anywhere in the driver. Remove it to clean up dead code and fix
a CamelCase warning.

Signed-off-by: Ethan Tidmore <ethantidmore06@gmail.com>
---
 drivers/staging/rtl8723bs/include/drv_types.h | 1 -
 drivers/staging/rtl8723bs/os_dep/os_intfs.c   | 1 -
 2 files changed, 2 deletions(-)

diff --git a/drivers/staging/rtl8723bs/include/drv_types.h b/drivers/staging/rtl8723bs/include/drv_types.h
index 00da21774c4d..11e1feade4e4 100644
--- a/drivers/staging/rtl8723bs/include/drv_types.h
+++ b/drivers/staging/rtl8723bs/include/drv_types.h
@@ -160,7 +160,6 @@ struct registry_priv {
 	u8 reg_enable_tx_power_by_rate;
 	u8 reg_power_base;
 	u8 reg_pwr_tbl_sel;
-	u8 RFE_Type;
 	u8  check_fw_ps;
 
 	u8 qos_opt_enable;
diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c b/drivers/staging/rtl8723bs/os_dep/os_intfs.c
index c163e2eeea26..f7f23d1b1709 100644
--- a/drivers/staging/rtl8723bs/os_dep/os_intfs.c
+++ b/drivers/staging/rtl8723bs/os_dep/os_intfs.c
@@ -263,7 +263,6 @@ static void loadparam(struct adapter *padapter, struct net_device *pnetdev)
 	registry_par->reg_enable_tx_power_by_rate = (u8)rtw_tx_pwr_by_rate;
 
 	registry_par->reg_power_base = 14;
-	registry_par->RFE_Type = 64;
 
 	registry_par->qos_opt_enable = (u8)rtw_qos_opt_enable;
 
-- 
2.52.0


      parent reply	other threads:[~2026-01-27  1:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  1:21 [PATCH v2 0/8] staging: rtl8723bs: rename members of struct registry_priv and remove dead code Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 1/8] staging: rtl8723bs: rename RegEnableTxPowerLimit to reg_enable_tx_power_limit Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 2/8] staging: rtl8723bs: rename RegEnableTxPowerByRate to reg_enable_tx_power_by_rate Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 3/8] staging: rtl8723bs: rename RegPowerBase to reg_power_base Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 4/8] staging: rtl8723bs: rename RegPwrTblSel to reg_pwr_tbl_sel Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 5/8] staging: rtl8723bs: remove unused variable TxBBSwing_2G Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 6/8] staging: rtl8723bs: remove unused variable AmplifierType_2G Ethan Tidmore
2026-01-27  1:21 ` [PATCH v2 7/8] staging: rtl8723bs: remove unused variable bEn_RFE Ethan Tidmore
2026-01-27  1:21 ` Ethan Tidmore [this message]

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=20260127012118.43037-9-ethantidmore06@gmail.com \
    --to=ethantidmore06@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --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 \
    /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