From: linux@treblig.org
To: arend.vanspriel@broadcom.com, kvalo@kernel.org,
linux-wireless@vger.kernel.org
Cc: brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn
Date: Thu, 26 Jun 2025 15:08:09 +0100 [thread overview]
Message-ID: <20250626140812.56700-1-linux@treblig.org> (raw)
From: "Dr. David Alan Gilbert" <linux@treblig.org>
Hi,
This set removes a bunch of unused functions in phy_cmn.c;
I've checked the history of most of them, and they look like they've
been unused since all the way back to 2010 when they were added
to staging.
There are a lot of them, so I've arbitrarily split it up into
convenient size chunks of about 10 functions each.
I see back in 2014, Rickard Strandqvist also tried to clean some
of this up, but I don't see any reply to that thread.
(Build tested only)
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
Dave
Dr. David Alan Gilbert (3):
wifi: brcm80211: Remove unused functions
wifi: brcm80211: Remove more unused functions
wifi: brcm80211: Remove yet more unused functions
.../broadcom/brcm80211/brcmsmac/phy/phy_cmn.c | 443 ------------------
.../broadcom/brcm80211/brcmsmac/phy/phy_hal.h | 27 --
.../broadcom/brcm80211/brcmsmac/phy/phy_int.h | 11 -
.../broadcom/brcm80211/brcmsmac/phy/phy_n.c | 19 -
4 files changed, 500 deletions(-)
--
2.50.0
next reply other threads:[~2025-06-26 14:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:08 linux [this message]
2025-06-26 14:08 ` [PATCH 1/3] wifi: brcm80211: Remove unused functions linux
2025-07-23 11:12 ` Arend van Spriel
2025-06-26 14:08 ` [PATCH 2/3] wifi: brcm80211: Remove more " linux
2025-07-23 11:13 ` Arend van Spriel
2025-06-26 14:08 ` [PATCH 3/3] wifi: brcm80211: Remove yet " linux
2025-07-23 11:13 ` Arend van Spriel
2025-06-27 7:11 ` [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn Johannes Berg
2025-06-27 17:51 ` Dr. David Alan Gilbert
2025-06-30 12:12 ` Johannes Berg
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=20250626140812.56700-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211@lists.linux.dev \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/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