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 1/5] staging: rtl8192e: renamed variable bAMSDU_Support
Date: Wed, 6 Dec 2023 18:04:00 -0500 [thread overview]
Message-ID: <20231206230404.1721-2-garyrookard@fastmail.org> (raw)
In-Reply-To: <20231206230404.1721-1-garyrookard@fastmail.org>
Coding style issue, checkpatch Avoid CamelCase,
rename it. bAMSDU_Suppport -> amsdu_support
Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
---
drivers/staging/rtl8192e/rtl819x_HT.h | 2 +-
drivers/staging/rtl8192e/rtl819x_HTProc.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/rtl8192e/rtl819x_HT.h b/drivers/staging/rtl8192e/rtl819x_HT.h
index 5018c3905be8..e02fa40262bd 100644
--- a/drivers/staging/rtl8192e/rtl819x_HT.h
+++ b/drivers/staging/rtl8192e/rtl819x_HT.h
@@ -107,7 +107,7 @@ struct rt_hi_throughput {
struct ht_info_ele SelfHTInfo;
u8 PeerHTCapBuf[32];
u8 PeerHTInfoBuf[32];
- u8 bAMSDU_Support;
+ u8 amsdu_support;
u16 amsdu_max_size;
u8 bCurrent_AMSDU_Support;
u16 nCurrent_AMSDU_MaxSize;
diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
index 6475832f23f6..b2f2e1c0cf6b 100644
--- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
+++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
@@ -82,7 +82,7 @@ void ht_update_default_setting(struct rtllib_device *ieee)
ht_info->reg_supp_cck = true;
ht_info->amsdu_max_size = 7935UL;
- ht_info->bAMSDU_Support = 0;
+ ht_info->amsdu_support = 0;
ht_info->bAMPDUEnable = 1;
ht_info->AMPDU_Factor = 2;
@@ -489,7 +489,7 @@ void HTOnAssocRsp(struct rtllib_device *ieee)
((pPeerHTCap->DssCCk == 1) ? true :
false) : false);
- ht_info->bCurrent_AMSDU_Support = ht_info->bAMSDU_Support;
+ ht_info->bCurrent_AMSDU_Support = ht_info->amsdu_support;
nMaxAMSDUSize = (pPeerHTCap->MaxAMSDUSize == 0) ? 3839 : 7935;
--
2.41.0
next prev parent reply other threads:[~2023-12-06 23:03 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 ` Gary Rookard [this message]
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 ` [PATCH 4/5] staging: rtl8192e: renamed variable MPDU_Density Gary Rookard
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-2-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