public inbox for linux-staging@lists.linux.dev
 help / color / mirror / Atom feed
From: Ethan Tidmore <ethantidmore06@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Michael Straube <straube.linux@gmail.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Ethan Tidmore <ethantidmore06@gmail.com>
Subject: [PATCH v2 0/4] staging: rtl8723bs: remove unused diagnostic
Date: Tue, 27 Jan 2026 18:40:04 -0600	[thread overview]
Message-ID: <20260128004009.51095-1-ethantidmore06@gmail.com> (raw)

This series performs a driver-wide audit and cleanup of dead diagnostic 
code within the rtl8723bs staging driver.

The vendor-originated code included a variety of diagnostic counters 
housed within 'struct debug_priv'. These counters were updated 
throughout the driver's hot paths—including MLME, receive, power 
control, and SDIO allocation—but were never read, exposed via 
debugfs, or utilized for any internal logic.

This series removes the write-only counters, the skeletal functions 
used to update them, and cleans up the resulting unused pointers 
and logic blocks.

Changes in v2:
- Expanded the series to include the removal of RX FIFO overflow 
  logic in hal_com.c.

Ethan Tidmore (4):
  staging: rtl8723bs: remove dead RX info reset logic
  staging: rtl8723bs: remove dead RX FIFO overflow logic
  staging: rtl8723bs: remove dead RX sequence logic
  staging: rtl8723bs: remove unused struct debug_priv and all counters

 drivers/staging/rtl8723bs/core/rtw_mlme.c     | 12 -----
 drivers/staging/rtl8723bs/core/rtw_mlme_ext.c |  3 --
 drivers/staging/rtl8723bs/core/rtw_pwrctrl.c  |  6 +--
 drivers/staging/rtl8723bs/core/rtw_recv.c     | 23 +--------
 drivers/staging/rtl8723bs/hal/hal_com.c       | 19 --------
 drivers/staging/rtl8723bs/hal/rtl8723b_dm.c   |  7 ---
 .../staging/rtl8723bs/hal/rtl8723b_hal_init.c |  4 --
 drivers/staging/rtl8723bs/hal/sdio_halinit.c  |  8 +---
 drivers/staging/rtl8723bs/include/drv_types.h | 41 ----------------
 drivers/staging/rtl8723bs/include/hal_com.h   |  1 -
 drivers/staging/rtl8723bs/os_dep/os_intfs.c   | 14 ++----
 drivers/staging/rtl8723bs/os_dep/sdio_intf.c  | 48 +++++--------------
 12 files changed, 17 insertions(+), 169 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-01-28  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-28  0:40 Ethan Tidmore [this message]
2026-01-28  0:40 ` [PATCH v2 1/4] staging: rtl8723bs: remove dead RX info reset logic Ethan Tidmore
2026-01-28  0:40 ` [PATCH v2 2/4] staging: rtl8723bs: remove dead RX FIFO overflow logic Ethan Tidmore
2026-01-28  9:29   ` kernel test robot
2026-01-28  0:40 ` [PATCH v2 3/4] staging: rtl8723bs: remove dead RX sequence logic Ethan Tidmore
2026-01-28  0:40 ` [PATCH v2 4/4] staging: rtl8723bs: remove unused struct debug_priv and all counters Ethan Tidmore
2026-01-28 11:02 ` [PATCH v2 0/4] staging: rtl8723bs: remove unused diagnostic Greg Kroah-Hartman
2026-01-28 13:23 ` 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=20260128004009.51095-1-ethantidmore06@gmail.com \
    --to=ethantidmore06@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=straube.linux@gmail.com \
    /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