On Thu, 15 Oct 2026 12:28:14 +0100, Vincent Donnefort wrote:
> TRACE_REMOTE relies on tracefs, eventfs and ring-buffer which are only
> built and declared when TRACING is enabled. It is however possible for a
> config to have FTRACE=y TRACING=n and TRACE_REMOTE=y.
>
> To fix this configuration, have TRACE_REMOTE select TRACING directly,
> just like other FTRACE options do and drop the TRACING dependency from
> NVHE_EL2_TRACING to avoid a circular Kconfig dependency.
>
> [...]
Applied to fixes, thanks!
[1/1] tracing/remotes: Fix TRACE_REMOTE build when TRACING=n
commit: 3bb853ad84244f0b86ab12f029bc4a0c9c7100e8
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
