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 v2 0/2] staging: rtl8723bs: fix uint types in hal_intf and rtw_security
Date: Wed, 7 Oct 2026 01:37:49 +0530 [thread overview]
Message-ID: <20261006200751.819332-1-contact.pranavdesai@gmail.com> (raw)
Per Greg's feedback on v1, I went through the variables to pick
types based on how each is used, rather than doing a blind replace.
I am sending this as a smaller 2-patch series to ensure I am on the
right track before tackling the rest of the driver. If this approach
looks good, I will do the same for the remaining files.
Changes in v2:
- Replaced the driver-wide `uint` to `unsigned int` conversion with
explicit sizing (u8, u16, u32, bool) based on actual variable usage.
- Scoped down from the entire driver to just hal_intf and rtw_security
to keep review easy.
Link: https://lore.kernel.org/linux-staging/20261006102846.170825-1-contact.pranavdesai@gmail.com/
Pranav Desai (2):
staging: rtl8723bs: replace uint with u32 in hal_intf.[ch]
staging: rtl8723bs: replace uint with explicit types in rtw_security.c
drivers/staging/rtl8723bs/core/rtw_security.c | 51 +++++++++++--------
drivers/staging/rtl8723bs/hal/hal_intf.c | 8 +--
drivers/staging/rtl8723bs/include/hal_intf.h | 4 +-
3 files changed, 36 insertions(+), 27 deletions(-)
--
2.55.0
next reply other threads:[~2026-10-06 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 20:07 Pranav Desai [this message]
2026-10-06 20:07 ` [PATCH v2 1/2] staging: rtl8723bs: replace uint with u32 in hal_intf.[ch] Pranav Desai
2026-10-06 21:07 ` Greg KH
2026-10-07 12:31 ` Pranav Desai
2026-10-06 20:07 ` [PATCH v2 2/2] staging: rtl8723bs: replace uint with explicit types in rtw_security.c Pranav Desai
2026-10-06 21:06 ` Greg KH
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=20261006200751.819332-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®