[Intel-xe] ✓ CI.checkpatch: success for drm/xe: Internally change the compute_mode and no_dma_fence mode naming

[Patchwork]

== Series Details ==

Series: drm/xe: Internally change the compute_mode and no_dma_fence mode naming
URL   : https://patchwork.freedesktop.org/series/126913/
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
63c2b6b160bca2df6efc7bc4cea6f442097d7854
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit f0a4f371af99996bfda4e8f9e1069b2f344b9a81
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Mon Nov 27 13:33:49 2023 +0100

    drm/xe: Internally change the compute_mode and no_dma_fence mode naming
    
    The name "compute_mode" can be confusing since compute uses either this
    mode or fault_mode to achieve the long-running semantics, and compute_mode
    can, moving forward, enable fault_mode under the hood to work around
    hardware limitations.
    
    Also the name no_dma_fence_mode really refers to what we elsewhere call
    long-running mode and the mode contrary to what its name suggests allows
    dma-fences as in-fences.
    
    So in an attempt to be more consistent, rename
    no_dma_fence_mode -> lr_mode
    compute_mode      -> preempt_fence_mode
    
    And adjust flags so that
    
    preempt_fence_mode sets XE_VM_FLAG_LR_MODE
    fault_mode sets XE_VM_FLAG_LR_MODE | XE_VM_FLAG_FAULT_MODE
    
    v2:
    - Fix a typo in the commit message (Oak Zeng)
    
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Reviewed-by: Oak Zeng <oak.zeng at intel.com>
+ /mt/dim checkpatch 742c5e2bbe41df0e79309e7d601e3a52ef0a4e59 drm-intel
f0a4f371a drm/xe: Internally change the compute_mode and no_dma_fence mode naming