From: Steven Rostedt <rostedt@goodmis.org>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tom Zanussi <zanussi@kernel.org>,
pengdonglin <pengdonglin@xiaomi.com>,
Shengming Hu <hu.shengming@zte.com.cn>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: make tr->d_max_latency accessible without CONFIG_FSNOTIFY
Date: Wed, 11 Feb 2026 12:51:52 -0500 [thread overview]
Message-ID: <20260211125152.3afe6e4f@fedora> (raw)
In-Reply-To: <20260210141310.1605322-1-arnd@kernel.org>
On Tue, 10 Feb 2026 15:13:06 +0100
Arnd Bergmann <arnd@kernel.org> wrote:
> From: Arnd Bergmann <arnd@arndb.de>
>
> A recent change attempted to make the tracing_max_latency file visible
> unconditionally, but this lead to a build failure:
>
> kernel/trace/trace.c: In function 'trace_create_maxlat_file':
> kernel/trace/trace.c:1543:13: error: 'struct trace_array' has no member named 'd_max_latency'; did you mean 'max_latency'?
> 1543 | tr->d_max_latency = trace_create_file("tracing_max_latency",
> | ^~~~~~~~~~~~~
>
> Make the corresponding change in the header file.
>
> Fixes: ba73713da50e ("tracing: Clean up use of trace_create_maxlat_file()")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Beat you to it ;-)
https://lore.kernel.org/linux-trace-kernel/20260209194631.788bfc85@fedora/
-- Steve
next prev parent reply other threads:[~2026-02-11 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 14:13 [PATCH] tracing: make tr->d_max_latency accessible without CONFIG_FSNOTIFY Arnd Bergmann
2026-02-11 17:51 ` Steven Rostedt [this message]
2026-02-11 18:15 ` 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=20260211125152.3afe6e4f@fedora \
--to=rostedt@goodmis.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=hu.shengming@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pengdonglin@xiaomi.com \
--cc=zanussi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.