From: Jad Keskes <inasj268@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Jad Keskes <inasj268@gmail.com>
Subject: [PATCH 3/3] staging: rtl8723bs: remove unused RF_PATH_MAX_90_8812 define
Date: Fri, 19 Jun 2026 09:37:36 +0100 [thread overview]
Message-ID: <20260619083736.577096-3-inasj268@gmail.com> (raw)
In-Reply-To: <20260619083736.577096-1-inasj268@gmail.com>
Remove RF_PATH_MAX_90_8812 which is a leftover from RTL8812
chip support and is not referenced anywhere in this driver.
Signed-off-by: Jad Keskes <inasj268@gmail.com>
---
drivers/staging/rtl8723bs/include/hal_phy.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/rtl8723bs/include/hal_phy.h b/drivers/staging/rtl8723bs/include/hal_phy.h
index abc0f27fdaa4..f7dfed0614d7 100644
--- a/drivers/staging/rtl8723bs/include/hal_phy.h
+++ b/drivers/staging/rtl8723bs/include/hal_phy.h
@@ -39,7 +39,6 @@ enum rf_path {
#define TX_4S 3
#define RF_PATH_MAX_92C_88E 2
-#define RF_PATH_MAX_90_8812 4 /* Max RF number 90 support */
enum wireless_mode {
WIRELESS_MODE_UNKNOWN = 0x00,
--
2.54.0
next prev parent reply other threads:[~2026-06-19 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 8:37 [PATCH 1/3] staging: rtl8723bs: remove unused rtl8192c function declarations Jad Keskes
2026-06-19 8:37 ` [PATCH 2/3] staging: rtl8723bs: remove unused AMPDU burst mode values Jad Keskes
2026-06-19 8:37 ` Jad Keskes [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-18 20:56 [PATCH 1/3] staging: rtl8723bs: remove unused rtl8192c function declarations Jad Keskes
2026-06-18 20:56 ` [PATCH 3/3] staging: rtl8723bs: remove unused RF_PATH_MAX_90_8812 define Jad Keskes
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=20260619083736.577096-3-inasj268@gmail.com \
--to=inasj268@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.