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 1/3] staging: rtl8723bs: remove unused rtl8192c function declarations
Date: Thu, 18 Jun 2026 21:56:01 +0100 [thread overview]
Message-ID: <20260618205603.452858-1-inasj268@gmail.com> (raw)
Remove two function declarations from rtl8192c_recv.h that have no
implementation and are never called in the rtl8723bs driver:
- rtl8192c_translate_rx_signal_stuff()
- rtl8192c_query_rx_desc_status()
These are leftovers from the original Realtek multi-chip codebase
and relate to the RTL8192C family, not the RTL8723B.
Signed-off-by: Jad Keskes <inasj268@gmail.com>
---
drivers/staging/rtl8723bs/include/rtl8192c_recv.h | 4 ----
1 file changed, 4 deletions(-)
diff --git a/drivers/staging/rtl8723bs/include/rtl8192c_recv.h b/drivers/staging/rtl8723bs/include/rtl8192c_recv.h
index e2e9aa03ffdf..b63625ab4e45 100644
--- a/drivers/staging/rtl8723bs/include/rtl8192c_recv.h
+++ b/drivers/staging/rtl8723bs/include/rtl8192c_recv.h
@@ -30,8 +30,4 @@ struct phy_stat {
/* Rx smooth factor */
#define Rx_Smooth_Factor (20)
-
-void rtl8192c_translate_rx_signal_stuff(union recv_frame *precvframe, struct phy_stat *pphy_status);
-void rtl8192c_query_rx_desc_status(union recv_frame *precvframe, struct recv_stat *pdesc);
-
#endif
--
2.54.0
next reply other threads:[~2026-06-18 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 20:56 Jad Keskes [this message]
2026-06-18 20:56 ` [PATCH 2/3] staging: rtl8723bs: remove unused AMPDU burst mode values for other chips 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=20260618205603.452858-1-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox