From: Johannes Berg <johannes@sipsolutions.net>
To: Steven Rostedt <rostedt@kernel.org>, linux-kernel@vger.kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [for-next][PATCH 4/4] cfg80211: Remove unused tracepoints
Date: Wed, 01 Oct 2025 16:49:29 +0200 [thread overview]
Message-ID: <1a4ee34782868893a237ba70e518dca17147f013.camel@sipsolutions.net> (raw)
In-Reply-To: <20251001144625.373974129@kernel.org>
On Wed, 2025-10-01 at 10:46 -0400, Steven Rostedt wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> Tracepoints that are defined take up around 5K each, even if they are not
> used. If they are defined and not used, then they waste memory for unused
> code. Soon unused tracepoints will cause warnings.
>
> Remove the unused tracepoints of the cfg80211 subsystem. They are:
>
> cfg80211_chandef_dfs_required
> cfg80211_return_u32
> cfg80211_return_uint
> cfg80211_send_rx_auth
This is in net-next [1], should go to Linus's tree whenever that is
pulled [2].
[1] https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=58febb47b961a91d0d12ee0c1618a7843c0908ce
[2] https://lore.kernel.org/lkml/20251001131156.27805-1-pabeni@redhat.com/
johannes
next prev parent reply other threads:[~2025-10-01 14:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 14:46 [for-next][PATCH 0/4] tracing: Removed unused tracepoints for v6.18 Steven Rostedt
2025-10-01 14:46 ` [for-next][PATCH 1/4] cdns2: Remove unused tracepoints Steven Rostedt
2025-10-01 14:46 ` [for-next][PATCH 2/4] cdns3: " Steven Rostedt
2025-10-01 14:46 ` [for-next][PATCH 3/4] cdnsp: " Steven Rostedt
2025-10-01 14:46 ` [for-next][PATCH 4/4] cfg80211: " Steven Rostedt
2025-10-01 14:49 ` Johannes Berg [this message]
2025-10-01 15:14 ` Steven Rostedt
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=1a4ee34782868893a237ba70e518dca17147f013.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=rostedt@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®