From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: [PATCH 10/10] staging: rtl8192e: Remove constant variable reg_rx_reorder_enable
Date: Wed, 13 Dec 2023 17:52:55 +0100 [thread overview]
Message-ID: <c9bf183b78bfe1fc242dc496786cd0c9f20262a4.1702406712.git.philipp.g.hortmann@gmail.com> (raw)
In-Reply-To: <cover.1702406712.git.philipp.g.hortmann@gmail.com>
Remove constant variable reg_rx_reorder_enable and replace it at the place
of usage with the value.
Signed-off-by: Philipp Hortmann <philipp.g.hortmann@gmail.com>
---
drivers/staging/rtl8192e/rtl819x_HT.h | 1 -
drivers/staging/rtl8192e/rtl819x_HTProc.c | 3 +--
2 files changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_HT.h b/drivers/staging/rtl8192e/rtl819x_HT.h
index 514ac9e1f3f8..2911ea82dd17 100644
--- a/drivers/staging/rtl8192e/rtl819x_HT.h
+++ b/drivers/staging/rtl8192e/rtl819x_HT.h
@@ -115,7 +115,6 @@ struct rt_hi_throughput {
u8 current_rt2rt_aggregation;
u8 current_rt2rt_long_slot_time;
u8 sz_rt2rt_agg_buf[10];
- u8 reg_rx_reorder_enable;
u8 cur_rx_reorder_enable;
u8 rx_reorder_win_size;
u8 rx_reorder_pending_time;
diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
index d9561e3a76d6..00bf5c706157 100644
--- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
+++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
@@ -79,7 +79,6 @@ void ht_update_default_setting(struct rtllib_device *ieee)
ieee->tx_enable_fw_calc_dur = 1;
- ht_info->reg_rx_reorder_enable = 1;
ht_info->rx_reorder_win_size = 64;
ht_info->rx_reorder_pending_time = 30;
}
@@ -484,7 +483,7 @@ void HTOnAssocRsp(struct rtllib_device *ieee)
if (ht_info->iot_action & HT_IOT_ACT_TX_USE_AMSDU_8K) {
ht_info->current_ampdu_enable = false;
}
- ht_info->cur_rx_reorder_enable = ht_info->reg_rx_reorder_enable;
+ ht_info->cur_rx_reorder_enable = 1;
if (pPeerHTCap->MCS[0] == 0)
pPeerHTCap->MCS[0] = 0xff;
--
2.43.0
prev parent reply other threads:[~2023-12-13 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 16:51 [PATCH 00/10] staging: rtl8192e: Remove variable nMaxAMSDUSize and further Philipp Hortmann
2023-12-13 16:51 ` [PATCH 01/10] staging: rtl8192e: Remove variable bCurrent_AMSDU_Support Philipp Hortmann
2023-12-13 16:51 ` [PATCH 02/10] staging: rtl8192e: Remove unused variable nMaxAMSDUSize Philipp Hortmann
2023-12-13 16:51 ` [PATCH 03/10] staging: rtl8192e: Remove constant variable self_mimo_ps Philipp Hortmann
2023-12-13 16:52 ` [PATCH 04/10] staging: rtl8192e: Remove constant variable peer_mimo_ps Philipp Hortmann
2023-12-13 16:52 ` [PATCH 05/10] staging: rtl8192e: Remove constant variable forced_short_gi Philipp Hortmann
2023-12-13 16:52 ` [PATCH 06/10] staging: rtl8192e: Remove unused variable ht_info->amsdu_support Philipp Hortmann
2023-12-13 16:52 ` [PATCH 07/10] staging: rtl8192e: Remove variable ht_info->mpdu_density Philipp Hortmann
2023-12-13 16:52 ` [PATCH 08/10] staging: rtl8192e: Remove variable ht_info->RT2RT_HT_Mode Philipp Hortmann
2023-12-13 16:52 ` [PATCH 09/10] staging: rtl8192e: Remove constant variable reg_rt2rt_aggregation Philipp Hortmann
2023-12-13 16:52 ` Philipp Hortmann [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=c9bf183b78bfe1fc242dc496786cd0c9f20262a4.1702406712.git.philipp.g.hortmann@gmail.com \
--to=philipp.g.hortmann@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 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®