[Intel-xe] ✓ CI.checkpatch: success for drm/xe/vm, drm/xe/uapi: Use LR abbrev for long-running vms

[Patchwork]

== Series Details ==

Series: drm/xe/vm, drm/xe/uapi: Use LR abbrev for long-running vms
URL   : https://patchwork.freedesktop.org/series/126273/
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 62288c33d2f87645252a448dcaaa71b8c9b8e4f1
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Fri Nov 10 14:59:13 2023 +0100

    drm/xe/vm, drm/xe/uapi: Use LR abbrev for long-running vms
    
    Currently we're using "compute mode" for long running VMs using
    using preempt-fences for memory management, and "fault mode" for long
    running VMs using page faults. Internally the driver uses "no_dma_fences"
    for long-running vms which is a bit misleading since dma-fences are only
    disallowed as out-fences.
    
    Change this to use the terminology "long-running" abbreviated as LR for
    long-running VMs. These VMs can then either be in preempt-fence mode or
    fault mode. The user can force fault mode at creation time, but otherwise
    the driver can choose to use fault- or preempt-fence mode for long-running
    vms depending on the device capabilities. Initially unless fault-mode is
    specified, the driver uses preempt-fence mode.
    
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Cc: Francois Dugast <francois.dugast at intel.com>
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
+ /mt/dim checkpatch b3890fb4386dcef68a96888141c4cc773f6241ce drm-intel
62288c33d drm/xe/vm, drm/xe/uapi: Use LR abbrev for long-running vms