From: Steven Rostedt <rostedt@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-xfs@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>,
Carlos Maiolino <cem@kernel.org>, Christoph Hellwig <hch@lst.de>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: [PATCH 0/4] xfs: more unused events from linux-next
Date: Tue, 22 Jul 2025 16:19:07 -0400 [thread overview]
Message-ID: <20250722201907.886429445@kernel.org> (raw)
I reran the unused tracepoint code on the latest linux-next and found more
xfs trace events. One was recently added but the rest were there before. Not
sure how I missed them.
But anyway, here's a few more patches to remove unused xfs trace events.
Steven Rostedt (4):
xfs: remove unused trace event xfs_dqreclaim_dirty
xfs: remove unused trace event xfs_log_cil_return
xfs: remove unused trace event xfs_discard_rtrelax
xfs: remove unused trace event xfs_reflink_cow_enospc
----
fs/xfs/xfs_trace.h | 4 ----
1 file changed, 4 deletions(-)
next reply other threads:[~2025-07-22 20:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 20:19 Steven Rostedt [this message]
2025-07-22 20:19 ` [PATCH 1/4] xfs: remove unused trace event xfs_dqreclaim_dirty Steven Rostedt
2025-07-22 20:19 ` [PATCH 2/4] xfs: remove unused trace event xfs_log_cil_return Steven Rostedt
2025-07-22 20:19 ` [PATCH 3/4] xfs: remove unused trace event xfs_discard_rtrelax Steven Rostedt
2025-07-22 20:19 ` [PATCH 4/4] xfs: remove unused trace event xfs_reflink_cow_enospc Steven Rostedt
2025-07-22 23:28 ` [PATCH 0/4] xfs: more unused events from linux-next Darrick J. Wong
2025-07-22 23:57 ` Steven Rostedt
2025-07-23 5:41 ` Christoph Hellwig
2025-07-23 15:01 ` Carlos Maiolino
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=20250722201907.886429445@kernel.org \
--to=rostedt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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
Powered by JetHome