From: Tree Davies <tdavies@darkphysics.net>
To: gregkh@linuxfoundation.org, philipp.g.hortmann@gmail.com,
dan.carpenter@linaro.org
Cc: tdavies@darkphysics.net, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: [PATCH] staging: rtl8192e: Rename variable bRegShortGI40MHz
Date: Wed, 5 Jul 2023 19:16:38 -0700 [thread overview]
Message-ID: <ZKYkBlqcydh26zSo@kimchi.darkphysics> (raw)
This patch renames variable bRegShortGI40MHz to breg_short_gi_40MHz
to fix checkpatch warning Avoid CamelCase.
Signed-off-by: Tree Davies <tdavies@darkphysics.net>
---
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 2bbd01048561..07102ce5ef5d 100644
--- a/drivers/staging/rtl8192e/rtl819x_HT.h
+++ b/drivers/staging/rtl8192e/rtl819x_HT.h
@@ -96,7 +96,7 @@ struct rt_hi_throughput {
u8 bCurrentHTSupport;
u8 bRegBW40MHz;
u8 bCurBW40MHz;
- u8 bRegShortGI40MHz;
+ u8 breg_short_gi_40MHz;
u8 bCurShortGI40MHz;
u8 bRegShortGI20MHz;
u8 bCurShortGI20MHz;
diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
index f9fa3f2bb728..1844098a4308 100644
--- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
+++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
@@ -72,7 +72,7 @@ void HTUpdateDefaultSetting(struct rtllib_device *ieee)
struct rt_hi_throughput *ht_info = ieee->ht_info;
ht_info->bRegShortGI20MHz = 1;
- ht_info->bRegShortGI40MHz = 1;
+ ht_info->breg_short_gi_40MHz = 1;
ht_info->bRegBW40MHz = 1;
@@ -545,7 +545,7 @@ void HTOnAssocRsp(struct rtllib_device *ieee)
ht_info->bCurShortGI20MHz = ((ht_info->bRegShortGI20MHz) ?
((pPeerHTCap->ShortGI20Mhz == 1) ?
true : false) : false);
- ht_info->bCurShortGI40MHz = ((ht_info->bRegShortGI40MHz) ?
+ ht_info->bCurShortGI40MHz = ((ht_info->breg_short_gi_40MHz) ?
((pPeerHTCap->ShortGI40Mhz == 1) ?
true : false) : false);
@@ -781,7 +781,7 @@ void HTUseDefaultSetting(struct rtllib_device *ieee)
ht_info->bCurBW40MHz = ht_info->bRegBW40MHz;
ht_info->bCurShortGI20MHz = ht_info->bRegShortGI20MHz;
- ht_info->bCurShortGI40MHz = ht_info->bRegShortGI40MHz;
+ ht_info->bCurShortGI40MHz = ht_info->breg_short_gi_40MHz;
if (ieee->iw_mode == IW_MODE_ADHOC)
ieee->current_network.qos_data.active =
--
2.30.2
reply other threads:[~2023-07-06 2:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZKYkBlqcydh26zSo@kimchi.darkphysics \
--to=tdavies@darkphysics.net \
--cc=dan.carpenter@linaro.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