public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
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: rename variable EWC11NHTCap
Date: Sun,  7 Jan 2024 22:22:32 -0500	[thread overview]
Message-ID: <20240108032233.4280-5-garyrookard@fastmail.org> (raw)
In-Reply-To: <20240108032233.4280-1-garyrookard@fastmail.org>

Coding style issue, checkpatch Avoid CamelCase,
rename it. EWC11NHTCap -> ewc_11n_ht_cap

Signed-off-by: Gary Rookard <garyrookard@fastmail.org>
---
 drivers/staging/rtl8192e/rtl819x_HTProc.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/rtl8192e/rtl819x_HTProc.c b/drivers/staging/rtl8192e/rtl819x_HTProc.c
index fe066d39b563..5598e74187cd 100644
--- a/drivers/staging/rtl8192e/rtl819x_HTProc.c
+++ b/drivers/staging/rtl8192e/rtl819x_HTProc.c
@@ -241,9 +241,9 @@ void ht_construct_capability_element(struct rtllib_device *ieee, u8 *pos_ht_cap,
 	memset(pos_ht_cap, 0, *len);
 
 	if ((assoc) && (ht->peer_ht_spec_ver == HT_SPEC_VER_EWC)) {
-		static const u8	EWC11NHTCap[] = { 0x00, 0x90, 0x4c, 0x33 };
+		static const u8	ewc_11n_ht_cap[] = { 0x00, 0x90, 0x4c, 0x33 };
 
-		memcpy(pos_ht_cap, EWC11NHTCap, sizeof(EWC11NHTCap));
+		memcpy(pos_ht_cap, ewc_11n_ht_cap, sizeof(ewc_11n_ht_cap));
 		cap_ele = (struct ht_capab_ele *)&pos_ht_cap[4];
 		*len = 30 + 2;
 	} else {
-- 
2.43.0


  parent reply	other threads:[~2024-01-08  3:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08  3:22 [PATCH 0/5] staging: rtl8192e: renamed variable is40MHz and 4 other Gary Rookard
2024-01-08  3:22 ` [PATCH 1/5] staging: rtl8192e: rename variable is40MHz Gary Rookard
2024-01-08  7:58   ` Dan Carpenter
2024-01-08 13:22     ` Gary Rookard
     [not found]       ` <62836460ae502097ca8307bcee85a5ae3634e1acc74af843ffc466c28d1a0b95@mu.id>
2024-01-09  1:25         ` Gary Rookard
2024-01-09  7:43           ` Dan Carpenter
2024-01-08  3:22 ` [PATCH 2/5] staging: rtl8192e: rename variable isShortGI Gary Rookard
2024-01-08  3:22 ` [PATCH 3/5] staging: rtl8192e: rename variable retValue Gary Rookard
2024-01-08  3:22 ` Gary Rookard [this message]
2024-01-08  3:22 ` [PATCH 5/5] staging: rtl8192e: rename variable AdvCoding Gary Rookard
2024-01-08  4:46 ` [PATCH 0/5] staging: rtl8192e: renamed variable is40MHz and 4 other 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=20240108032233.4280-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