From: Steven Rostedt <rostedt@goodmis.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-trace-kernel@vger.kernel.org, linux-kernel@vger.kernel.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com
Subject: Re: [PATCH] trace: ftrace_dump_on_oops[] is not exported, make it static
Date: Tue, 6 Jan 2026 18:41:32 -0500 [thread overview]
Message-ID: <20260106184132.23a73aca@gandalf.local.home> (raw)
In-Reply-To: <20260106231054.84270-1-ben.dooks@codethink.co.uk>
On Tue, 6 Jan 2026 23:10:54 +0000
Ben Dooks <ben.dooks@codethink.co.uk> wrote:
> The ftrace_dump_on_oops string is not used outside of trace.c so
> make it static to avoid the export warning from sparse:
>
> kernel/trace/trace.c:141:6: warning: symbol 'ftrace_dump_on_oops' was not declared. Should it be static?
>
This could probably have:
Fixes: dd293df6395a2 ("tracing: Move trace sysctls into trace.c")
as that was the commit to move the usage of that variable back into the
defining file.
-- Steve
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> ---
> kernel/trace/trace.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
> index 6f2148df14d9..5c196ea93768 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -138,7 +138,7 @@ cpumask_var_t __read_mostly tracing_buffer_mask;
> * by commas.
> */
> /* Set to string format zero to disable by default */
> -char ftrace_dump_on_oops[MAX_TRACER_SIZE] = "0";
> +static char ftrace_dump_on_oops[MAX_TRACER_SIZE] = "0";
>
> /* When set, tracing will stop when a WARN*() is hit */
> static int __disable_trace_on_warning;
prev parent reply other threads:[~2026-01-06 23:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 23:10 [PATCH] trace: ftrace_dump_on_oops[] is not exported, make it static Ben Dooks
2026-01-06 23:41 ` Steven Rostedt [this message]
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=20260106184132.23a73aca@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=ben.dooks@codethink.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--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