From: Stepan Ionichev <sozdayvek@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
luka.gejak@linux.dev, Stepan Ionichev <sozdayvek@gmail.com>
Subject: [PATCH v2] staging: rtl8723bs: drop blank line before close brace in rtw_ieee80211.c
Date: Sat, 2 May 2026 13:50:18 +0500 [thread overview]
Message-ID: <20260502085018.1440-1-sozdayvek@gmail.com> (raw)
In-Reply-To: <20260501165917.1504-1-sozdayvek@gmail.com>
Drop a blank line before a close brace in rtw_get_wapi_ie(),
flagged by checkpatch.pl:
CHECK: Blank lines aren't necessary before a close brace '}'
No functional change.
Signed-off-by: Stepan Ionichev <sozdayvek@gmail.com>
---
v2:
- Rebased onto staging-next, as suggested by Luka Gejak.
- Dropped the rtw_btcoex.c and rtw_efuse.c hunks: already addressed by
commit 7dbc9fd71438 ("staging: rtl8723bs: remove multiple blank lines
in core/").
- Narrowed subject to reflect the remaining single-file scope.
drivers/staging/rtl8723bs/core/rtw_ieee80211.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c b/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
index 72b7f731d..5fb1fe5b7 100644
--- a/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
+++ b/drivers/staging/rtl8723bs/core/rtw_ieee80211.c
@@ -593,7 +593,6 @@ int rtw_get_wapi_ie(u8 *in_ie, uint in_len, u8 *wapi_ie, u16 *wapi_len)
if (wapi_len)
*wapi_len = in_ie[cnt + 1] + 2;
-
}
cnt += in_ie[cnt + 1] + 2; /* get next */
--
2.33.0.windows.2
prev parent reply other threads:[~2026-05-02 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 16:59 [PATCH] staging: rtl8723bs: drop duplicate blank lines in core files Stepan Ionichev
2026-05-01 18:53 ` Luka Gejak
2026-05-02 8:50 ` Stepan Ionichev [this message]
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=20260502085018.1440-1-sozdayvek@gmail.com \
--to=sozdayvek@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=luka.gejak@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