✗ CI.checkpatch: warning for drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP

[Patchwork]

== Series Details ==

Series: drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP
URL   : https://patchwork.freedesktop.org/series/135370/
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
51ce9f6cd981d42d7467409d7dbc559a450abc1e
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 379196c649b1fca8c64adccb5376147c6ad13428
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
Date:   Tue Jun 25 23:38:42 2024 +0800

    drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP
    
    Per client engine utilization uses RING_TIMESTAMP to return drm-total-cycles to
    the user. Current code uses XE_FW_GT to read this register on the first
    available engine in a GT. When testing on DG2, it is observed that this value is
    0 when running test on some engines. To resolve that, get the hwe domain
    specific FW for reading the engine timestamp.
    
    v2:
    - update commit message
    - use domain specific FW (Matt)
    
    Fixes: 188ced1e0ff8 ("drm/xe/client: Print runtime to fdinfo")
    Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
+ /mt/dim checkpatch 61dfb30a52fac9b1bb455a250799611682334cc3 drm-intel
379196c649b1 drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP
-:6: WARNING:COMMIT_LOG_LONG_LINE: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#6: 
Per client engine utilization uses RING_TIMESTAMP to return drm-total-cycles to

total: 0 errors, 1 warnings, 0 checks, 32 lines checked