From: Pranav Desai <contact.pranavdesai@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Pranav Desai <contact.pranavdesai@gmail.com>
Subject: [PATCH v3 0/6] staging: rtl8723bs: explicitly type variables in rtw_security.c
Date: Wed, 7 Oct 2026 17:23:36 +0530 [thread overview]
Message-ID: <20261007115342.1121742-1-contact.pranavdesai@gmail.com> (raw)
This v3 series focuses exclusively on explicitly typing the non-standard
'uint' variables in rtw_security.c.
Per Greg's feedback on v2, I have split the explicit sizing of variables
into 6 granular, logical commits to ensure rigorous bisectability and
ease of review:
- Patch 1: Matches packet lengths to struct definitions.
- Patch 2: Converts integer flags to standard booleans and updates 1/0 assignments.
- Patch 3: Explicitly sizes frame types to u8 based on bitmasks.
- Patches 4-6: Explicitly types computed variables, iterators, and helper
lengths to safely handle math operations.
Changes in v3:
- Split rtw_security.c changes into 6 logical patches (one concept per patch).
- Replaced 1/0 assignments with true/false for boolean flags.
- Dropped hal_intf.c from this series entirely (will address separately).
Link: https://lore.kernel.org/linux-staging/20261006200751.819332-1-contact.pranavdesai@gmail.com/
Pranav Desai (6):
staging: rtl8723bs: use explicit types for lengths in rtw_security.c
staging: rtl8723bs: use bool for flags in rtw_security.c
staging: rtl8723bs: use u8 for frame types in rtw_security.c
staging: rtl8723bs: use explicit types for math variables and
iterators
staging: rtl8723bs: use u32 for payload_length in rtw_security.c
staging: rtl8723bs: use u32 for length variables in rtw_BIP_verify()
drivers/staging/rtl8723bs/core/rtw_security.c | 68 ++++++++++---------
1 file changed, 37 insertions(+), 31 deletions(-)
--
2.55.0
next reply other threads:[~2026-10-07 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 11:53 Pranav Desai [this message]
2026-10-07 11:53 ` [PATCH v3 1/6] staging: rtl8723bs: use explicit types for lengths " Pranav Desai
2026-10-07 11:53 ` [PATCH v3 2/6] staging: rtl8723bs: use bool for flags " Pranav Desai
2026-10-07 11:53 ` [PATCH v3 3/6] staging: rtl8723bs: use u8 for frame types " Pranav Desai
2026-10-07 11:53 ` [PATCH v3 4/6] staging: rtl8723bs: use explicit types for math variables and iterators Pranav Desai
2026-10-07 11:53 ` [PATCH v3 5/6] staging: rtl8723bs: use u32 for payload_length in rtw_security.c Pranav Desai
2026-10-07 11:53 ` [PATCH v3 6/6] staging: rtl8723bs: use u32 for length variables in rtw_BIP_verify() Pranav Desai
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=20261007115342.1121742-1-contact.pranavdesai@gmail.com \
--to=contact.pranavdesai@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
/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
all inboxes | Powered by JetHome®