Subject: linux-next: manual merge of the driver-core tree with the drm tree

From: [email-masked]
Date: Mon, 26 Sep 2022 22:11:02 +0100

Hi all,

Today's linux-next merge of the driver-core tree got a conflict in:

  drivers/gpu/drm/Kconfig

between commits:

  ba8f16cd08190 ("drm: selftest: convert drm_damage_helper selftest to KUnit")
  fc8d29e298cf4 ("drm: selftest: convert drm_mm selftest to KUnit")

from the drm tree and commit:

  84ec67288c10f ("drm_print: wrap drm_*_dbg in dyndbg descriptor factory macro")

from the driver-core 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.

diff --cc drivers/gpu/drm/Kconfig
index 198ba846d34bf,2438e0dccfa16..0000000000000
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@@ -51,9 -50,22 +51,21 @@@ config DRM_DEBUG_M
  
  	  If in doubt, say "N".
  
+ config DRM_USE_DYNAMIC_DEBUG
+ 	bool "use dynamic debug to implement drm.debug"
+ 	default y
+ 	depends on DRM
+ 	depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
+ 	depends on JUMP_LABEL
+ 	help
+ 	  Use dynamic-debug to avoid drm_debug_enabled() runtime overheads.
+ 	  Due to callsite counts in DRM drivers (~4k in amdgpu) and 56
+ 	  bytes per callsite, the .data costs can be substantial, and
+ 	  are therefore configurable.
+ 
 -config DRM_DEBUG_SELFTEST
 -	tristate "kselftests for DRM"
 -	depends on DRM
 -	depends on DEBUG_KERNEL
 +config DRM_KUNIT_TEST
 +	tristate "KUnit tests for DRM" if !KUNIT_ALL_TESTS
 +	depends on DRM && KUNIT
  	select PRIME_NUMBERS
  	select DRM_DISPLAY_DP_HELPER
  	select DRM_DISPLAY_HELPER