On Thu, 13 Mar 2025 at 19:44, Alessandro Carminati wrote:
>
> From: Guenter Roeck
>
> Add unit tests to verify that warning backtrace suppression works.
>
> If backtrace suppression does _not_ work, the unit tests will likely
> trigger unsuppressed backtraces, which should actually help to get
>
On Thu, 13 Mar 2025 at 19:44, Alessandro Carminati wrote:
>
> From: Guenter Roeck
>
> Some unit tests intentionally trigger warning backtraces by passing
> bad parameters to API functions. Such unit tests typically check the
> return value from those calls, not the existence of the warning backtr
Michal Suchanek writes:
> Similar to x86 the ppc boot code does not build with GCC 15.
>
> Copy the fix from
> commit ee2ab467bddf ("x86/boot: Use '-std=gnu11' to fix build with GCC 15")
>
> Signed-off-by: Michal Suchanek
> ---
> v2: Move the fix outside of ifdef to apply to all subarchitectures
On Thu, 13 Mar 2025 at 19:44, Alessandro Carminati wrote:
>
> From: Guenter Roeck
>
> Add name of functions triggering warning backtraces to the __bug_table
> object section to enable support for suppressing WARNING backtraces.
>
> To limit image size impact, the pointer to the function name is o
On Thu, 13 Mar 2025 at 19:44, Alessandro Carminati wrote:
>
> From: Guenter Roeck
>
> Count suppressed warning backtraces to enable code which suppresses
> warning backtraces to check if the expected backtrace(s) have been
> observed.
>
> Using atomics for the backtrace count resulted in build er
