Hello:
This series was applied to riscv/linux.git (fixes)
by Shuah Khan <[email protected]>:
On Fri, 15 May 2026 14:29:31 +0200 you wrote:
> Some unit tests intentionally trigger warning backtraces by passing bad
> parameters to kernel API functions. Such unit tests typically check the
> return value from such calls, not the existence of the warning backtrace.
>
> Such intentionally generated warning backtraces are neither desirable
> nor useful for a number of reasons:
> - They can result in overlooked real problems.
> - A warning that suddenly starts to show up in unit tests needs to be
> investigated and has to be marked to be ignored, for example by
> adjusting filter scripts. Such filters are ad hoc because there is
> no real standard format for warnings. On top of that, such filter
> scripts would require constant maintenance.
>
> [...]
Here is the summary with links:
- [v13,1/4] bug/kunit: Core support for suppressing warning backtraces
(no matching commit)
- [v13,2/4] kunit: Add backtrace suppression self-tests
(no matching commit)
- [v13,3/4] drm: Suppress intentional warning backtraces in scaling unit tests
(no matching commit)
- [v13,4/4] kunit: Add documentation for warning backtrace suppression API
https://git.kernel.org/riscv/c/5c1553dd5db3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
