From mboxrd@z Thu Jan 1 00:00:00 1970 From: Claude Code Review Bot To: dri-devel-reviews@example.com Subject: Claude review: drm/msm/dpu: Don't use %pK through printk (again) Date: Tue, 24 Feb 2026 10:32:44 +1000 Message-ID: In-Reply-To: <20260223-restricted-pointers-msm-v1-1-14c0b451e372@linutronix.de> References: <20260223-restricted-pointers-msm-v1-1-14c0b451e372@linutronix.de> <20260223-restricted-pointers-msm-v1-1-14c0b451e372@linutronix.de> X-Mailer: Claude Code Patch Reviewer Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Patch Review > - DRM_ERROR("invalid ctx %pK gc base\n", ctx); > + DRM_ERROR("invalid ctx %p gc base\n", ctx); Straightforward `%pK` to `%p` conversion. No issues. The commit message is well-written: it explains the rationale (why `%pK` is problematic), references the original cleanup commit (1ba9fbe40337) and the commit that reintroduced the usage (39a750ff5fc9). Dmitry's review reply also suggests adding a `Fixes:` tag for the latter commit, which would be a good addition for backporting purposes. One minor note: the error message itself (`"invalid ctx %p gc base"`) is somewhat confusing -- it's the `gc.base` field that is invalid (zero), not `ctx` itself. But that's pre-existing text not introduced by this patch, so not relevant to this review. No issues found in this patch. --- Generated by Claude Code Patch Reviewer