From: Michael Straube <straube.linux@gmail.com>
To: gregkh@linuxfoundation.org
Cc: philipp.g.hortmann@gmail.com, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org,
Michael Straube <straube.linux@gmail.com>
Subject: [PATCH 5/5] staging: rtl8192e: adjust size of RxMIMOSignalStrength
Date: Sat, 31 Aug 2024 12:08:09 +0200 [thread overview]
Message-ID: <20240831100809.29173-6-straube.linux@gmail.com> (raw)
In-Reply-To: <20240831100809.29173-1-straube.linux@gmail.com>
The array RxMIMOSignalStrength in struct rtllib_rx_stats is always accessed
with indices in the range i = 0; i < 2. We can reduce the size from 4 to 2.
Signed-off-by: Michael Straube <straube.linux@gmail.com>
---
drivers/staging/rtl8192e/rtllib.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/rtl8192e/rtllib.h b/drivers/staging/rtl8192e/rtllib.h
index 7a1a68317a49..0eb987e999c5 100644
--- a/drivers/staging/rtl8192e/rtllib.h
+++ b/drivers/staging/rtl8192e/rtllib.h
@@ -480,7 +480,7 @@ struct rtllib_rx_stats {
bool bFirstMPDU;
bool contain_htc;
u32 RxPWDBAll;
- u8 RxMIMOSignalStrength[4];
+ u8 RxMIMOSignalStrength[2];
s8 RxMIMOSignalQuality[2];
bool bPacketMatchBSSID;
bool bIsCCK;
--
2.46.0
next prev parent reply other threads:[~2024-08-31 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 10:08 [PATCH 0/5] staging: rtl8192e: remove RF90_PATH_{C,D} Michael Straube
2024-08-31 10:08 ` [PATCH 1/5] staging: rtl8192e: remove RF90_PATH_{C,D} from enum rf90_radio_path Michael Straube
2024-08-31 10:08 ` [PATCH 2/5] staging: rtl8192e: adjust size of rx_pwr for new RF90_PATH_MAX Michael Straube
2024-08-31 10:08 ` [PATCH 3/5] staging: rtl8192e: adjust size of trsw_gain_X " Michael Straube
2024-08-31 10:08 ` [PATCH 4/5] staging: rtl8192e: adjust size of brfpath_rxenable " Michael Straube
2024-08-31 10:08 ` Michael Straube [this message]
2024-09-02 17:37 ` [PATCH 0/5] staging: rtl8192e: remove RF90_PATH_{C,D} 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=20240831100809.29173-6-straube.linux@gmail.com \
--to=straube.linux@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.