* [for-trace:latency/for-next PATCH] rv: Fix compilation if !CONFIG_RV_REACTORS
[not found] <c4bb3aa4a73c0ec815bdc30c104b6f90fae5ed39.camel@redhat.com>
@ 2025-11-13 15:06 ` Gabriele Monaco
0 siblings, 0 replies; only message in thread
From: Gabriele Monaco @ 2025-11-13 15:06 UTC (permalink / raw)
To: rostedt, Steven Rostedt, Gabriele Monaco, Thomas Weißschuh,
linux-trace-kernel, linux-kernel
Cc: lkp, oe-kbuild-all
The kernel test robot spotted a compilation error if reactors are
disabled.
Fix the warning by keeping LTL monitor variable as always static.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202511131948.vxi5mdjU-lkp@intel.com/
Fixes: 4f739ed19d22 ("rv: Pass va_list to reactors")
Signed-off-by: Gabriele Monaco <gmonaco@redhat.com>
---
This patch fixes a patch that was just merged to trace:latency/for-next.
It builds locally with both configurations. I started another kernel
robot run and, if it passes, I'm going to send a pull request with only
this.
include/rv/ltl_monitor.h | 5 -----
1 file changed, 5 deletions(-)
diff --git a/include/rv/ltl_monitor.h b/include/rv/ltl_monitor.h
index 00c42b36f961..eff60cd61106 100644
--- a/include/rv/ltl_monitor.h
+++ b/include/rv/ltl_monitor.h
@@ -17,12 +17,7 @@
#endif
#define RV_MONITOR_NAME CONCATENATE(rv_, MONITOR_NAME)
-
-#ifdef CONFIG_RV_REACTORS
static struct rv_monitor RV_MONITOR_NAME;
-#else
-extern struct rv_monitor RV_MONITOR_NAME;
-#endif
static int ltl_monitor_slot = RV_PER_TASK_MONITOR_INIT;
base-commit: 69d8895cb9a9f6450374577af8584c2e21cb5a9f
--
2.51.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2025-11-13 15:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <c4bb3aa4a73c0ec815bdc30c104b6f90fae5ed39.camel@redhat.com>
2025-11-13 15:06 ` [for-trace:latency/for-next PATCH] rv: Fix compilation if !CONFIG_RV_REACTORS Gabriele Monaco
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).