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

[Patchwork]

== Series Details ==

Series: drm/xe: Log unreliable MMIO reads during forcewake (rev2)
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 1d01bb4f1a0ae3d0e4c1515acf764587c9dc22bd
Author: Shuicheng Lin <shuicheng.lin at intel.com>
Date:   Thu Oct 17 03:40:26 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.
    
    v2 (Matt Brost):
      - set ret value (-EIO) to kick the error to upper layers
    
    Suggested-by: Alex Zuo <alex.zuo at intel.com>
    Signed-off-by: Shuicheng Lin <shuicheng.lin at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray at intel.com>
    Cc: Matt Roper <matthew.d.roper at intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch 87312f4bbb70018f831a8ef565db9cdc37b4da67 drm-intel
1d01bb4f1a0a drm/xe: Log unreliable MMIO reads during forcewake