✗ CI.checkpatch: warning for Introduce DRM device wedged event (rev4)

[Patchwork]

== Series Details ==

Series: Introduce DRM device wedged event (rev4)
URL   : https://patchwork.freedesktop.org/series/138070/
State : warning

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2ca30f47b83ffe5b0f7443d7bd01878d96e0335c
Author: Raag Jadav <raag.jadav at intel.com>
Date:   Mon Sep 23 09:28:26 2024 +0530

    drm/i915: Use device wedged event
    
    Now that we have device wedged event supported by DRM core, make use
    of it. With this in place, userspace will be notified of wedged device
    on gt reset failure.
    
    Signed-off-by: Raag Jadav <raag.jadav at intel.com>
+ /mt/dim checkpatch d5334f14ce6ca46c6537184c69e4e352ff6d7750 drm-intel
a7da80eb1eb3 drm: Introduce device wedged event
-:81: WARNING:STATIC_CONST_CHAR_ARRAY: char * array declaration might be better as static const
#81: FILE: drivers/gpu/drm/drm_drv.c:527:
+	char *envp[] = { event_string, NULL };

total: 0 errors, 1 warnings, 0 checks, 123 lines checked
88d4be5c5cc0 drm: Expose wedge recovery methods
a56e0b9e6f59 drm/xe: Use device wedged event
-:19: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#19: 
KERNEL[265.802982] change   /devices/pci0000:00/0000:00:01.0/0000:01:00.0/0000:02:01.0/0000:03:00.0/drm/card0 (drm)

total: 0 errors, 1 warnings, 0 checks, 53 lines checked
2ca30f47b83f drm/i915: Use device wedged event