From: Gary Rookard <garyrookard@fastmail.org>
To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Gary Rookard <garyrookard@fastmail.org>
Subject: [PATCH 4/5] staging: rtl8192e: renamed variable MPDU_Density
Date: Wed, 6 Dec 2023 18:04:03 -0500 [thread overview]
Message-ID: <20231206230404.1721-5-garyrookard@fastmail.org> (raw)
In-Reply-To: <20231206230404.1721-1-garyrookard@fastmail.org>
Coding style issue, checkpatch Avoid CamelCase,
rename it. MPDU_Density -> mpdu_density
Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
---
drivers/staging/rtl8192e/rtl819x_HT.h | 2 +-
drivers/staging/rtl8192e/rtl819x_HTProc.c | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_HT.h b/drivers/staging/rtl8192e/rtl819x_HT.h
index c01ccf252924..98c1e5840e31 100644
--- a/drivers/staging/rtl8192e/rtl819x_HT.h
+++ b/drivers/staging/rtl8192e/rtl819x_HT.h
@@ -115,7 +115,7 @@ struct rt_hi_throughput {
u8 current_ampdu_enable;
u8 ampdu_factor;
u8 CurrentAMPDUFactor;
- u8 MPDU_Density;
+ u8 mpdu_density;
u8 current_mpdu_density;
enum ht_aggre_mode ForcedAMPDUMode;
u8 forced_ampdu_factor;
diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
index 0f044356e428..72b30d4df5f7 100644
--- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
+++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
@@ -86,7 +86,7 @@ void ht_update_default_setting(struct rtllib_device *ieee)
ht_info->ampdu_enable = 1;
ht_info->ampdu_factor = 2;
- ht_info->MPDU_Density = 0;
+ ht_info->mpdu_density = 0;
ht_info->self_mimo_ps = 3;
if (ht_info->self_mimo_ps == 2)
@@ -525,7 +525,7 @@ void HTOnAssocRsp(struct rtllib_device *ieee)
HT_AGG_SIZE_32K);
}
}
- ht_info->current_mpdu_density = max_t(u8, ht_info->MPDU_Density,
+ ht_info->current_mpdu_density = max_t(u8, ht_info->mpdu_density,
pPeerHTCap->MPDUDensity);
if (ht_info->iot_action & HT_IOT_ACT_TX_USE_AMSDU_8K) {
ht_info->current_ampdu_enable = false;
@@ -570,7 +570,7 @@ void HTInitializeHTInfo(struct rtllib_device *ieee)
ht_info->bCurrent_AMSDU_Support = false;
ht_info->nCurrent_AMSDU_MaxSize = ht_info->amsdu_max_size;
- ht_info->current_mpdu_density = ht_info->MPDU_Density;
+ ht_info->current_mpdu_density = ht_info->mpdu_density;
ht_info->CurrentAMPDUFactor = ht_info->ampdu_factor;
memset((void *)(&ht_info->SelfHTCap), 0,
--
2.41.0
next prev parent reply other threads:[~2023-12-06 23:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 23:03 [PATCH 0/5] staging: rtl8192e: this patch series renames (5) different variables Gary Rookard
2023-12-06 23:04 ` [PATCH 1/5] staging: rtl8192e: renamed variable bAMSDU_Support Gary Rookard
2023-12-06 23:04 ` [PATCH 2/5] staging: rtl8192e: renamed variable bAMPDUEnable Gary Rookard
2023-12-06 23:04 ` [PATCH 3/5] staging: rtl8192e: renamed variable AMPDU_Factor Gary Rookard
2023-12-06 23:04 ` Gary Rookard [this message]
2023-12-06 23:04 ` [PATCH 5/5] staging: rtl8192e: renamed variable bTxEnableFwCalcDur Gary Rookard
2023-12-07 17:37 ` [PATCH 0/5] staging: rtl8192e: this patch series renames (5) different variables Philipp Hortmann
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=20231206230404.1721-5-garyrookard@fastmail.org \
--to=garyrookard@fastmail.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=philipp.g.hortmann@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