From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH] tracing: Fix #if CONFIG_MODULES to #ifdef CONFIG_MODULES
Date: Mon, 20 Jan 2025 13:09:00 -0500 [thread overview]
Message-ID: <20250120130900.09a5ffba@gandalf.local.home> (raw)
In-Reply-To: <20250120125745.4ac90ca6@gandalf.local.home>
On Mon, 20 Jan 2025 12:57:45 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: Steven Rostedt <rostedt@goodmis.org>
>
> A typo was introduced when adding the ":mod:" command that did
> a "#if CONFIG_MODULES" instead of a "#ifdef CONFIG_MODULES".
> Fix it.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://lore.kernel.org/oe-kbuild-all/202501110319.xY9ltUxL-lkp@intel.com/
Cut and paste error. Wrong closes: Should have been:
Closes: https://lore.kernel.org/oe-kbuild-all/202501190121.E2CIJuUj-lkp@intel.com/
-- Steve
> Fixes: b355247df104e ("tracing: Cache ":mod:" events for modules not loaded yet")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace_events.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index f762e554fad4..bb1406719c3f 100644
> --- a/kernel/trace/trace_events.c
> +++ b/kernel/trace/trace_events.c
> @@ -857,7 +857,7 @@ static int ftrace_event_enable_disable(struct trace_event_file *file,
> return __ftrace_event_enable_disable(file, enable, 0);
> }
>
> -#if CONFIG_MODULES
> +#ifdef CONFIG_MODULES
> struct event_mod_load {
> struct list_head list;
> char *module;
prev parent reply other threads:[~2025-01-20 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 17:57 [PATCH] tracing: Fix #if CONFIG_MODULES to #ifdef CONFIG_MODULES Steven Rostedt
2025-01-20 18:09 ` 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=20250120130900.09a5ffba@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=torvalds@linux-foundation.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