From: linux@treblig.org
To: johannes@sipsolutions.net, linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH 0/2] wifi: mac80211: Deadcode cleanup
Date: Tue, 24 Dec 2024 01:32:55 +0000 [thread overview]
Message-ID: <20241224013257.185742-1-linux@treblig.org> (raw)
From: "Dr. David Alan Gilbert" <linux@treblig.org>
Hi,
This pair of patches removes a bunch of functions that haven't
been called for more than a few years.
I suspect I could go further; in particular I wonder
if
ieee80211_debugfs_key_remove_beacon_default()
and
ieee80211_debugfs_key_remove_mgmt_default()
could go together with a data structure somewhere?
Also, ieee80211_nan_func_match() was the last use of
cfg80211_nan_match(); but that would be in a separate area.
Dave
Dr. David Alan Gilbert (2):
wifi: mac80211: Clean up debugfs_key deadcode
wifi: mac80211: Remove unused ieee80211_nan_func_match
include/net/mac80211.h | 15 ------------
net/mac80211/cfg.c | 25 --------------------
net/mac80211/debugfs_key.c | 47 --------------------------------------
net/mac80211/debugfs_key.h | 15 ------------
4 files changed, 102 deletions(-)
--
2.47.1
next reply other threads:[~2024-12-24 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 1:32 linux [this message]
2024-12-24 1:32 ` [PATCH 1/2] wifi: mac80211: Clean up debugfs_key deadcode linux
2024-12-24 1:32 ` [PATCH 2/2] wifi: mac80211: Remove unused ieee80211_nan_func_match linux
2025-01-28 18:39 ` [PATCH 0/2] wifi: mac80211: Deadcode cleanup Dr. David Alan Gilbert
2025-01-28 19:33 ` Johannes Berg
2025-01-28 19:53 ` Dr. David Alan Gilbert
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=20241224013257.185742-1-linux@treblig.org \
--to=linux@treblig.org \
--cc=johannes@sipsolutions.net \
--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
all inboxes | Powered by JetHome®