Linux kernel staging patches
 help / color / mirror / Atom feed
From: Subhrojyoti Bala <subhrojyoti0609@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Subhrojyoti Bala <subhrojyoti0609@gmail.com>
Subject: [PATCH 1/5] staging: rtl8723bs: Fix multi-line comment style in wlan_bssdef.h
Date: Tue, 16 Jun 2026 16:30:44 +0530	[thread overview]
Message-ID: <20260616110048.45541-2-subhrojyoti0609@gmail.com> (raw)
In-Reply-To: <20260616110048.45541-1-subhrojyoti0609@gmail.com>

Fix block comments that were not following the kernel's multi-line
comment style. Comments should use the following format:

/*
 * text
 */

No functional change.

Signed-off-by: Subhrojyoti Bala <subhrojyoti0609@gmail.com>
---
 drivers/staging/rtl8723bs/include/wlan_bssdef.h | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/drivers/staging/rtl8723bs/include/wlan_bssdef.h b/drivers/staging/rtl8723bs/include/wlan_bssdef.h
index 812a68394268..25ac996e73e3 100644
--- a/drivers/staging/rtl8723bs/include/wlan_bssdef.h
+++ b/drivers/staging/rtl8723bs/include/wlan_bssdef.h
@@ -31,10 +31,9 @@ enum ndis_802_11_network_type {
 	Ndis802_11NetworkTypeMax    /*  not a real type, defined as an upper bound */
 };
 
-/*
-	FW will only save the channel number in DSConfig.
-	ODI Handler will convert the channel number to freq. number.
-*/
+/* FW will only save the channel number in DSConfig. */
+/* ODI Handler will convert the channel number to freq. number. */
+
 struct ndis_802_11_conf {
 	u32 length;             /*  Length of structure */
 	u32 beacon_period;       /*  units are Kusec */
@@ -138,7 +137,8 @@ struct wlan_phy_info {
 
 struct wlan_bcn_info {
 	/* these infor get from rtw_get_encrypt_info when
-	 * * translate scan to UI */
+	 * translate scan to UI
+	 */
 	u8 encryp_protocol;/* ENCRYP_PROTOCOL_E: OPEN/WEP/WPA/WPA2/WAPI */
 	int group_cipher; /* WPA/WPA2 group cipher */
 	int pairwise_cipher;/* WPA/WPA2/WEP pairwise cipher */
@@ -150,8 +150,8 @@ struct wlan_bcn_info {
 };
 
 /* temporally add #pragma pack for structure alignment issue of
-*   struct wlan_bssid_ex and get_wlan_bssid_ex_sz()
-*/
+ * struct wlan_bssid_ex and get_wlan_bssid_ex_sz()
+ */
 struct wlan_bssid_ex {
 	u32  length;
 	u8 mac_address[ETH_ALEN];
-- 
2.54.0


  reply	other threads:[~2026-06-16 11:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-16 11:00 [PATCH 0/5] staging: rtl8723bs: Fix coding style issues in header files Subhrojyoti Bala
2026-06-16 11:00 ` Subhrojyoti Bala [this message]
2026-06-16 11:00 ` [PATCH 2/5] staging: rtl8723bs: Fix indentation in enum in rtw_mlme.h Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 3/5] staging: rtl8723bs: Fix block comment style " Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 4/5] staging: rtl8723bs: Fix multi-line " Subhrojyoti Bala
2026-06-16 11:00 ` [PATCH 5/5] staging: rtl8723bs: Fix whitespace in comments " Subhrojyoti Bala
2026-06-16 12:09 ` [PATCH 0/5] staging: rtl8723bs: Fix coding style issues in header files Greg Kroah-Hartman
2026-06-16 12:21 ` Dan Carpenter

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=20260616110048.45541-2-subhrojyoti0609@gmail.com \
    --to=subhrojyoti0609@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