[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250722195730.7eb30450@gandalf.local.home>
Date: Tue, 22 Jul 2025 19:57:30 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Steven Rostedt <rostedt@...nel.org>, linux-kernel@...r.kernel.org,
linux-trace-kernel@...r.kernel.org, linux-xfs@...r.kernel.org, Masami
Hiramatsu <mhiramat@...nel.org>, Mark Rutland <mark.rutland@....com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>, Andrew Morton
<akpm@...ux-foundation.org>, Carlos Maiolino <cem@...nel.org>, Christoph
Hellwig <hch@....de>
Subject: Re: [PATCH 0/4] xfs: more unused events from linux-next
On Tue, 22 Jul 2025 16:28:42 -0700
"Darrick J. Wong" <djwong@...nel.org> wrote:
> On Tue, Jul 22, 2025 at 04:19:07PM -0400, Steven Rostedt wrote:
> >
> > 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
>
> I can directly take responsibility for 1, 3, and 4 -- those aren't going
> to come back. Patch 2 looks like an accidental add, and if anyone wants
> it they can always add it back.
>
> Reviewed-by: "Darrick J. Wong" <djwong@...nel.org>
Thanks. I'm guessing this will also go through the xfs tree?
-- Steve
Powered by blists - more mailing lists