From: luka.gejak@linux.dev
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Luka Gejak <luka.gejak@linux.dev>,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Dan Carpenter <error27@gmail.com>
Subject: [PATCH 09/11] staging: rtl8723bs: os_dep: remove unnecessary braces
Date: Mon, 13 Apr 2026 12:14:30 +0200 [thread overview]
Message-ID: <20260413101432.158925-10-luka.gejak@linux.dev> (raw)
In-Reply-To: <20260413101432.158925-1-luka.gejak@linux.dev>
From: Luka Gejak <luka.gejak@linux.dev>
Remove unnecessary braces around single-statement blocks in the os_dep
directory to adhere to the Linux kernel coding style. This resolves
unnecessary braces warnings reported by checkpatch.pl.
Signed-off-by: Luka Gejak <luka.gejak@linux.dev>
---
drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c | 3 +--
drivers/staging/rtl8723bs/os_dep/sdio_intf.c | 3 +--
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
index eb407d245ebc..53b305443c29 100644
--- a/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
+++ b/drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.c
@@ -1402,9 +1402,8 @@ static int rtw_cfg80211_set_key_mgt(struct security_priv *psecuritypriv, u32 key
if (key_mgt == WLAN_AKM_SUITE_8021X)
/* auth_type = UMAC_AUTH_TYPE_8021X; */
psecuritypriv->dot11AuthAlgrthm = dot11AuthAlgrthm_8021X;
- else if (key_mgt == WLAN_AKM_SUITE_PSK) {
+ else if (key_mgt == WLAN_AKM_SUITE_PSK)
psecuritypriv->dot11AuthAlgrthm = dot11AuthAlgrthm_8021X;
- }
return 0;
}
diff --git a/drivers/staging/rtl8723bs/os_dep/sdio_intf.c b/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
index 95523c3a508b..5c546ce04747 100644
--- a/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
+++ b/drivers/staging/rtl8723bs/os_dep/sdio_intf.c
@@ -144,9 +144,8 @@ static void sdio_deinit(struct dvobj_priv *dvobj)
sdio_claim_host(func);
sdio_disable_func(func);
- if (dvobj->irq_alloc) {
+ if (dvobj->irq_alloc)
sdio_release_irq(func);
- }
sdio_release_host(func);
}
--
2.53.0
next prev parent reply other threads:[~2026-04-13 10:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 10:14 [PATCH 00/11] staging: rtl8723bs: coding style cleanups luka.gejak
2026-04-13 10:14 ` [PATCH 01/11] staging: rtl8723bs: core: fix spacing around operators and casts luka.gejak
2026-04-13 10:14 ` [PATCH 02/11] staging: rtl8723bs: hal: " luka.gejak
2026-04-13 10:14 ` [PATCH 03/11] staging: rtl8723bs: os_dep: fix spacing around operators luka.gejak
2026-04-13 10:14 ` [PATCH 04/11] staging: rtl8723bs: core: align parameters with open parenthesis luka.gejak
2026-04-13 10:14 ` [PATCH 05/11] staging: rtl8723bs: hal: " luka.gejak
2026-04-13 10:14 ` [PATCH 06/11] staging: rtl8723bs: os_dep: " luka.gejak
2026-04-13 10:14 ` [PATCH 07/11] staging: rtl8723bs: core: remove blank lines before closing brace luka.gejak
2026-04-13 10:14 ` [PATCH 08/11] staging: rtl8723bs: hal: " luka.gejak
2026-04-13 10:14 ` luka.gejak [this message]
2026-04-13 10:14 ` [PATCH 10/11] staging: rtl8723bs: os_dep: remove blank lines before closing braces luka.gejak
2026-04-13 10:14 ` [PATCH 11/11] staging: rtl8723bs: hal: remove unnecessary braces luka.gejak
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=20260413101432.158925-10-luka.gejak@linux.dev \
--to=luka.gejak@linux.dev \
--cc=error27@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