✓ CI.checkpatch: success for drm/xe: Log unreliable MMIO reads during forcewake

[Patchwork]

== Series Details ==

Series: drm/xe: Log unreliable MMIO reads during forcewake
URL   : https://patchwork.freedesktop.org/series/139922/
State : success

== 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 efb1cc35a6da6df16053ddf22a602891a1f488a9
Author: Shuicheng Lin <shuicheng.lin at intel.com>
Date:   Sat Oct 12 03:34:45 2024 +0000

    drm/xe: Log unreliable MMIO reads during forcewake
    
    In some cases, when the driver attempts to read an MMIO register,
    the hardware may return 0xFFFFFFFF. The current force wake path
    code treats this as a valid response, as it only checks the BIT.
    However, 0xFFFFFFFF should be considered an invalid value, indicating
    a potential issue. To address this, we should add a log entry to
    highlight this condition.
    
    Suggested-by: Alex Zuo <alex.zuo at intel.com>
    Signed-off-by: Shuicheng Lin <shuicheng.lin at intel.com>
+ /mt/dim checkpatch 8dcf653f89accb0339e9dbbd84227a4527b2441d drm-intel
efb1cc35a6da drm/xe: Log unreliable MMIO reads during forcewake