✗ CI.checkpatch: warning for drm/xe: Use VF_CAP_REG for device wmb

[Patchwork]

== Series Details ==

Series: drm/xe: Use VF_CAP_REG for device wmb
URL   : https://patchwork.freedesktop.org/series/135663/
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 5004de368e665d898c1049106f33a2a552805d61
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Tue Jul 2 20:37:04 2024 +0200

    drm/xe: Use VF_CAP_REG for device wmb
    
    To force a write barrier on the device memory, we write to the
    SOFTWARE_FLAGS_SPR33 register, but this particular register was
    selected because it was one of the writable and unused register.
    
    Since a write barrier should also work if we use the read-only
    register, switch to VF_CAP_REG register that is also marked as
    accessible for VFs.
    
    While at it, add simple kernel-doc for xe_device_wmb() function.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Matt Roper <matthew.d.roper at intel.com>
+ /mt/dim checkpatch 5ca7296d32d5ea4fd002b6adfe05ffda6d654993 drm-intel
6c4157ac8084 drm/xe: Fix register definition order in xe_regs.h
c41fe2167650 drm/xe: Kill regs/xe_sriov_regs.h
-:60: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#60: 
deleted file mode 100644

total: 0 errors, 1 warnings, 0 checks, 60 lines checked
5004de368e66 drm/xe: Use VF_CAP_REG for device wmb