mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adriano Cordova <adrianox@gmail.com>
To: gregkh@linuxfoundation.org
Cc: linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
	Adriano Cordova <adrianox@gmail.com>
Subject: [PATCH 0/2] staging: rtl8723bs: remove dead chip code
Date: Sun, 30 Aug 2026 22:05:55 -0400	[thread overview]
Message-ID: <20260831020557.1235504-1-adrianox@gmail.com> (raw)

These two patches remove code in the rtl8723bs driver that is never
compiled or never referenced, with no change in behavior.

The first patch removes declarations guarded by BEAMFORMING_SUPPORT,
which is defined to 0, so they never reach the compiler. Preprocessing
the driver confirms the symbols are absent from the preprocessed output.

The second patch removes enums and defines left over from other Realtek
chips that are not referenced anywhere in the driver.

Compile-tested on x86. Rebuilding drivers/staging/rtl8723bs/ and
comparing all 55 '.o' files against the pre-change build shows every
object file is byte-for-byte identical.

Adriano Cordova <adrianox@gmail.com>

Adriano Cordova (2):
  staging: rtl8723bs: remove dead beamforming code
  staging: rtl8723bs: remove unused chip-type enums and defines

 drivers/staging/rtl8723bs/hal/odm.h              |  9 ---------
 .../staging/rtl8723bs/hal/odm_DynamicTxPower.h   |  1 -
 drivers/staging/rtl8723bs/hal/odm_precomp.h      |  1 -
 drivers/staging/rtl8723bs/include/hal_phy.h      | 16 ----------------
 4 files changed, 27 deletions(-)

-- 
2.51.0


             reply	other threads:[~2026-08-31  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  2:05 Adriano Cordova [this message]
2026-08-31  2:05 ` [PATCH 1/2] staging: rtl8723bs: remove dead beamforming code Adriano Cordova
2026-08-31  2:05 ` [PATCH 2/2] staging: rtl8723bs: remove unused chip-type enums and defines Adriano Cordova

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=20260831020557.1235504-1-adrianox@gmail.com \
    --to=adrianox@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

all inboxes | Powered by JetHome®