On Thu, 13 Mar 2025 11:43:15 +0000 Alessandro Carminati <acarm...@redhat.com> 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. I've had this series in mm.git's mm-new branch for a while. I didn't send it up for 6.15-rc1 due to what I believe to be unresolved review issues. I'll drop this v4 series. Please resend if/when suitable. Some notes I have taken are: https://lkml.kernel.org/r/202504190918.jlnurgvb-...@intel.com https://lkml.kernel.org/r/20250402074550.gq5...@noisy.programming.kicks-ass.net #arm64-add-support-for-suppressing-warning-backtraces.patch: check review Some fixes I had merged which presumably should be carried forward are https://lore.kernel.org/all/20250330212934.3f898c4c...@smtp.kernel.org/T/ https://lkml.kernel.org/r/20250330212739.85827c4c...@smtp.kernel.org Thanks.
