From: Joshua Gu <joshuagu789@gmail.com>
To: Ethan Tidmore <ethantidmore06@gmail.com>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [PATCH v2] staging: rtl8723bs: remove unnecessary spaces in rtw_security.c
Date: Mon, 16 Mar 2026 01:46:19 +0000 [thread overview]
Message-ID: <abdg69QDD_fwv3Sv@ubuntuarm64> (raw)
In-Reply-To: <DH3OX3CFT586.2HUDPSK7M65AS@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 0 bytes --]
[-- Attachment #2: 0001-staging-rtl8723bs-remove-unnecessary-spaces-in-rtw_s.patch --]
[-- Type: text/x-diff, Size: 1740 bytes --]
From 319ab64bc60820beedaabcd951cc9eb8f8c9bad4 Mon Sep 17 00:00:00 2001
From: Joshua Gu <joshuagu789@gmail.com>
Date: Sun, 15 Mar 2026 20:10:48 +0000
Subject: [PATCH v2] staging: rtl8723bs: remove unnecessary spaces in
rtw_security.c
Fix checkpatch.pl warnings about spaces after casts,
along with other double spaces.
Signed-off-by: Joshua Gu <joshuagu789@gmail.com>
---
Changes in v2:
- Removed double spaces after assignment operator in rtw_security.c
drivers/staging/rtl8723bs/core/rtw_security.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_security.c b/drivers/staging/rtl8723bs/core/rtw_security.c
index 54e89f192b18..b98bc1aa9cbe 100644
--- a/drivers/staging/rtl8723bs/core/rtw_security.c
+++ b/drivers/staging/rtl8723bs/core/rtw_security.c
@@ -658,8 +658,8 @@ static void construct_mic_iv(u8 *mic_iv,
for (i = 8; i < 14; i++)
mic_iv[i] = pn_vector[13 - i]; /* mic_iv[8:13] = PN[5:0] */
#endif
- mic_iv[14] = (unsigned char) (payload_length / 256);
- mic_iv[15] = (unsigned char) (payload_length % 256);
+ mic_iv[14] = (unsigned char)(payload_length / 256);
+ mic_iv[15] = (unsigned char)(payload_length % 256);
}
/************************************************/
@@ -781,8 +781,8 @@ static void construct_ctr_preload(u8 *ctr_preload,
for (i = 8; i < 14; i++)
ctr_preload[i] = pn_vector[13 - i]; /* ctr_preload[8:13] = PN[5:0] */
#endif
- ctr_preload[14] = (unsigned char) (c / 256); /* Ctr */
- ctr_preload[15] = (unsigned char) (c % 256);
+ ctr_preload[14] = (unsigned char)(c / 256); /* Ctr */
+ ctr_preload[15] = (unsigned char)(c % 256);
}
static signed int aes_cipher(u8 *key, uint hdrlen,
--
2.43.0
next prev parent reply other threads:[~2026-03-16 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 20:23 [PATCH] staging: rtl8723bs: remove unnecessary spaces in rtw_security.c Joshua Gu
2026-03-15 21:57 ` Ethan Tidmore
2026-03-16 1:46 ` Joshua Gu [this message]
2026-03-18 15:43 ` [PATCH v2] " Greg KH
-- strict thread matches above, loose matches on Subject: below --
2026-03-16 2:04 Joshua Gu
2026-03-16 3:33 ` Ethan Tidmore
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=abdg69QDD_fwv3Sv@ubuntuarm64 \
--to=joshuagu789@gmail.com \
--cc=ethantidmore06@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