[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230713163626.31338-18-jim.cromie@gmail.com>
Date: Thu, 13 Jul 2023 10:36:22 -0600
From: Jim Cromie <jim.cromie@...il.com>
To: jbaron@...mai.com, daniel.vetter@...ll.ch,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
amd-gfx@...ts.freedesktop.org, intel-gvt-dev@...ts.freedesktop.org,
intel-gfx@...ts.freedesktop.org
Cc: jani.nikula@...el.com, ville.syrjala@...ux.intel.com,
seanpaul@...omium.org, robdclark@...il.com,
gregkh@...uxfoundation.org, Jim Cromie <jim.cromie@...il.com>
Subject: [PATCH v4 17/21] drm: restore CONFIG_DRM_USE_DYNAMIC_DEBUG un-BROKEN
Lots of burn-in testing needed before signing, upstreaming.
I set default Y to maximize testing by default.
NOTE: without __UNIQUE_ID fix in HEAD~1, this population of
DRM_CLASSMAP_USE()rs experienced name collisions in several different
@lkp-robot allyes and randconfigs, probably because the macro is
always a file-scope declarator, and is always near the top of fhe
file. Moving declarations around tended to fix one collision, only to
create another collision elsewhere.
Signed-off-by: Jim Cromie <jim.cromie@...il.com>
---
drivers/gpu/drm/Kconfig | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index ba3fb04bb691..ff478fcba67e 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/gpu/drm/Kconfig
@@ -52,8 +52,7 @@ config DRM_DEBUG_MM
config DRM_USE_DYNAMIC_DEBUG
bool "use dynamic debug to implement drm.debug"
- default n
- depends on BROKEN
+ default y
depends on DRM
depends on DYNAMIC_DEBUG || DYNAMIC_DEBUG_CORE
depends on JUMP_LABEL
--
2.41.0
Powered by blists - more mailing lists