From: Steven Rostedt <rostedt@goodmis.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing: make tracepoint_printk static as not exported
Date: Thu, 2 Jul 2026 18:46:58 -0400 [thread overview]
Message-ID: <20260702184658.0e0ffb02@gandalf.local.home> (raw)
In-Reply-To: <20260617105822.904164-1-ben.dooks@codethink.co.uk>
On Wed, 17 Jun 2026 11:58:22 +0100
Ben Dooks <ben.dooks@codethink.co.uk> wrote:
> The tracepoint_printk symbol is not exported, so make it
> static to remove the following sparse warning:
>
> kernel/trace/trace.c:90:5: warning: symbol 'tracepoint_printk' was not declared. Should it be static?
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
Thanks, this became only used by this file via commit dd293df6395a2
("tracing: Move trace sysctls into trace.c")
I may add a Fixes tag to that commit.
-- Steve
> ---
> 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 6eb4d3097a4d..4c3729c8d5e2 100644
> --- a/kernel/trace/trace.c
> +++ b/kernel/trace/trace.c
> @@ -87,7 +87,7 @@ void __init disable_tracing_selftest(const char *reason)
>
> /* Pipe tracepoints to printk */
> static struct trace_iterator *tracepoint_print_iter;
> -int tracepoint_printk;
> +static int tracepoint_printk;
> static bool tracepoint_printk_stop_on_boot __initdata;
> static bool traceoff_after_boot __initdata;
> static DEFINE_STATIC_KEY_FALSE(tracepoint_printk_key);
next prev parent reply other threads:[~2026-07-02 22:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-17 10:58 [PATCH] tracing: make tracepoint_printk static as not exported Ben Dooks
2026-07-02 22:46 ` Steven Rostedt [this message]
2026-07-03 16:24 ` Ben Dooks
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=20260702184658.0e0ffb02@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