From: Jim Cromie <jim.cromie@gmail.com>
To: jbaron@akamai.com, daniel.vetter@ffwll.ch,
dri-devel@lists.freedesktop.org
Subject: [PATCH v5 20/23] drm: restore CONFIG_DRM_USE_DYNAMIC_DEBUG un-BROKEN
Date: Tue, 1 Aug 2023 17:35:10 -0600 [thread overview]
Message-ID: <20230801233515.166971-25-jim.cromie@gmail.com> (raw)
In-Reply-To: <20230801233515.166971-1-jim.cromie@gmail.com>
Lots of burn-in testing needed before signing, upstreaming.
NOTE: I set default Y to maximize testing by default.
Is there a better way to do this ?
Signed-off-by: Jim Cromie <jim.cromie@gmail.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
next prev parent reply other threads:[~2023-08-01 23:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 23:34 [PATCH v5 00/22] fix DRM_USE_DYNAMIC_DEBUG regression Jim Cromie
2023-08-01 23:34 ` [PATCH v5 01/23] drm: use correct ccflags-y syntax Jim Cromie
2023-08-01 23:34 ` [PATCH v5 02/23] test-dyndbg: fixup CLASSMAP usage error Jim Cromie
2023-08-01 23:34 ` [PATCH v5 03/23] dyndbg: make ddebug_class_param union members same size Jim Cromie
2023-08-01 23:34 ` [PATCH v5 04/23] dyndbg: replace classmap list with a vector Jim Cromie
2023-08-01 23:34 ` [PATCH v5 05/23] dyndbg: ddebug_apply_class_bitmap - add module arg, select on it Jim Cromie
2023-08-01 23:34 ` [PATCH v5 06/23] dyndbg: split param_set_dyndbg_classes to module/wrapper fns Jim Cromie
2023-08-01 23:34 ` [PATCH v5 07/23] dyndbg: drop NUM_TYPE_ARRAY Jim Cromie
2023-08-01 23:34 ` [PATCH v5 08/23] dyndbg: reduce verbose/debug clutter Jim Cromie
2023-08-01 23:34 ` [PATCH v5 09/23] dyndbg: silence debugs with no-change updates Jim Cromie
2023-08-01 23:34 ` [PATCH v5 10/23] dyndbg: tighten ddebug_class_name() 1st arg type Jim Cromie
2023-08-01 23:34 ` [PATCH v5 11/23] dyndbg: tighten fn-sig of ddebug_apply_class_bitmap Jim Cromie
2023-08-01 23:34 ` [PATCH v5 12/23] dyndbg-API: remove DD_CLASS_TYPE_(DISJOINT|LEVEL)_NAMES and code Jim Cromie
2023-08-01 23:34 ` [PATCH v5 13/22] checkpatch: file-scoped extern special case for linker-symbol Jim Cromie
2023-08-01 23:35 ` [PATCH v5 13/23] checkpatch: special case for file-scoped extern linker-symbol Jim Cromie
2023-08-01 23:35 ` [PATCH v5 14/23] dyndbg-API: fix CONFIG_DRM_USE_DYNAMIC_DEBUG regression Jim Cromie
2023-08-01 23:35 ` [PATCH v5 15/23] dyndbg: add for_each_boxed_vector Jim Cromie
2023-08-01 23:35 ` [PATCH v5 16/23] dyndbg: refactor ddebug_classparam_clamp_input Jim Cromie
2023-08-01 23:35 ` [PATCH v5 17/23] dyndbg-API: promote DYNDBG_CLASSMAP_PARAM to API Jim Cromie
2023-08-01 23:35 ` [PATCH v5 18/22] dyndbg-test: build it with just CONFIG_DYNAMIC_DEBUG_CORE Jim Cromie
2023-08-01 23:35 ` [PATCH v5 18/23] parens-on-PARAM Jim Cromie
2023-08-01 23:35 ` [PATCH v5 19/22] drm: restore CONFIG_DRM_USE_DYNAMIC_DEBUG un-BROKEN Jim Cromie
2023-08-01 23:35 ` [PATCH v5 19/23] dyndbg-test: build it with just CONFIG_DYNAMIC_DEBUG_CORE Jim Cromie
2023-08-01 23:35 ` [PATCH v5 20/22] drm-drivers: DRM_CLASSMAP_USE in 2nd batch of drivers, helpers Jim Cromie
2023-08-01 23:35 ` Jim Cromie [this message]
2023-08-01 23:35 ` [PATCH v5 21/23] " Jim Cromie
2023-08-01 23:35 ` [PATCH v5 21/22] dyndbg-doc: add classmap info to howto Jim Cromie
2023-08-01 23:35 ` [PATCH v5 22/22] checkpatch: reword long-line warn about commit-msg Jim Cromie
2023-08-01 23:55 ` Joe Perches
2023-08-01 23:35 ` [PATCH v5 22/23] dyndbg-doc: add classmap info to howto Jim Cromie
2023-08-01 23:35 ` [PATCH v5 23/23] checkpatch: reword long-line warn about commit-msg Jim Cromie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230801233515.166971-25-jim.cromie@gmail.com \
--to=jim.cromie@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbaron@akamai.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox