From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: linux@treblig.org, kvalo@kernel.org, linux-wireless@vger.kernel.org
Cc: brcm80211@lists.linux.dev, brcm80211-dev-list.pdl@broadcom.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] wifi: brcm80211: Remove unused functions
Date: Wed, 23 Jul 2025 13:12:58 +0200 [thread overview]
Message-ID: <8bad525e-420c-4870-a6dd-bd28dfd4708c@broadcom.com> (raw)
In-Reply-To: <20250626140812.56700-2-linux@treblig.org>
On 6/26/2025 4:08 PM, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> This is a subset of unused functions in bcrmsmac phy_cmn.c,
> They're unused since the original 2010
> commit a9533e7ea3c4 ("Staging: Add initial release of brcm80211 - Broadcom
> 802.11n wireless LAN driver.")
>
> Remove them.
> Then remove two more functions in phy_n.c that were only used
> by the ones just removed.
Tested on BCM4313 card.
Acked-by: Arend van Spriel <arend.vanspriel@broadcom.com>>
Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
> .../broadcom/brcm80211/brcmsmac/phy/phy_cmn.c | 128 ------------------
> .../broadcom/brcm80211/brcmsmac/phy/phy_hal.h | 11 --
> .../broadcom/brcm80211/brcmsmac/phy/phy_int.h | 8 --
> .../broadcom/brcm80211/brcmsmac/phy/phy_n.c | 19 ---
> 4 files changed, 166 deletions(-)
next prev parent reply other threads:[~2025-07-23 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 14:08 [PATCH 0/3] wifi: brcm80211: Deadcoding around phy_cmn linux
2025-06-26 14:08 ` [PATCH 1/3] wifi: brcm80211: Remove unused functions linux
2025-07-23 11:12 ` Arend van Spriel [this message]
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=8bad525e-420c-4870-a6dd-bd28dfd4708c@broadcom.com \
--to=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 \
--cc=linux@treblig.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