From mboxrd@z Thu Jan 1 00:00:00 1970 From: Claude Code Review Bot To: dri-devel-reviews@example.com Subject: Claude review: Fix DRM_USE_DYNAMIC_DEBUG=y Date: Sat, 14 Mar 2026 07:02:58 +1000 Message-ID: In-Reply-To: <20260313131045.2526422-1-jim.cromie@gmail.com> References: <20260313131045.2526422-1-jim.cromie@gmail.com> X-Mailer: Claude Code Patch Reviewer Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Overall Series Review Subject: Fix DRM_USE_DYNAMIC_DEBUG=3Dy Author: Jim Cromie Patches: 3 Reviewed: 2026-03-14T07:02:58.467847 --- This filtered mbox contains the cover letter (0/65) and the first 2 patches= of a 65-patch series "[PATCH v11 00/65] Fix DRM_USE_DYNAMIC_DEBUG=3Dy" by = Jim Cromie. The series aims to fix the long-standing regression (since Feb = 2023, commit bb2ff6c27bc9) where `DRM_USE_DYNAMIC_DEBUG=3Dy` was marked as = `BROKEN` because dyndbg classmaps didn't properly propagate `drm.debug=3D` from drm-core to driver modules. The two patches reviewed here are foundational preparatory changes =E2=80= =94 a linker script alignment fix and a code refactor. Both are reasonable = and well-motivated. The overall series is ambitious at 65 patches on v11, s= panning dyndbg core, linker scripts, DRM core, and many DRM drivers. This i= s a complex cross-subsystem change that has needed careful coordination. **Key concern for the series overall:** At 65 patches and v11, this needs t= o land soon or risk perpetual rebasing churn. The cover letter mentions CI = passing (pipeline #1622778), which is encouraging. The series would benefit= from explicit Reviewed-by/Acked-by tags from the dyndbg and linker-script = maintainers. --- Generated by Claude Code Patch Reviewer