Subject: linux-next: manual merge of the mm-hotfixes tree with Linus' tree

From: Stephen Rothwell <[email-masked]>
Date: Fri, 19 Apr 2024 09:32:22 +1000

Hi all,

Today's linux-next merge of the mm-hotfixes tree got a conflict in:

  tools/testing/selftests/kselftest_harness.h

between commit:

  caed8eba2215 ("selftests: kselftest_harness: fix Clang warning about zero-length format")

from Linus' tree and commit:

  52124c13ec1f ("selftests/harness: remove use of LINE_MAX")

from the mm-hotfixes-unstable branch of the mm-hotfixes tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc tools/testing/selftests/kselftest_harness.h
index ba3ddeda24bf,f0ae1f6466db..000000000000
--- a/tools/testing/selftests/kselftest_harness.h
+++ b/tools/testing/selftests/kselftest_harness.h
@@@ -1205,7 -1205,8 +1208,8 @@@ void __run_test(struct __fixture_metada
  		diagnostic = "unknown";
  
  	ksft_test_result_code(t->exit_code, test_name,
 -			      diagnostic ? "%s" : "", diagnostic);
 +			      diagnostic ? "%s" : NULL, diagnostic);
+ 	free(test_name);
  }
  
  static int test_harness_run(int argc, char **argv)