✓ CI.checkpatch: success for Refactor default device atomic settings (rev4)

[Patchwork]

== Series Details ==

Series: Refactor default device atomic settings (rev4)
URL   : https://patchwork.freedesktop.org/series/132930/
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
0daf0be5bb95eb0a0e42275e00a0e42d8d8fd543
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit beac6e1551b920817abe4ce43c4f28c515467567
Author: Nirmoy Das <nirmoy.das at intel.com>
Date:   Fri Apr 26 12:56:55 2024 +0200

    drm/xe: Refactor default device atomic settings
    
    The default behavior of device atomics depends on the
    VM type and buffer allocation types. Device atomics are
    expected to function with all types of allocations for
    traditional applications/APIs. Additionally, in compute/SVM
    API scenarios with fault mode or LR mode VMs, device atomics
    must work with single-region allocations. In all other cases
    device atomics should be disabled by default also on platforms
    where we know device atomics doesn't on work on particular
    allocations types.
    
    v2: Fix platform checks to correct atomics behaviour on PVC.
    
    Signed-off-by: Nirmoy Das <nirmoy.das at intel.com>
+ /mt/dim checkpatch cd4e45440e6710d7a1d097cd2fbac455bdecb68a drm-intel
48095b8d863e drm/xe: Introduce has_atomic_enable_pte_bit device info
6475dfe935d9 drm/xe: Move vm bind bo validation to a helper function
ed97938df90e drm/xe: Introduce has_device_atomics_on_smem device info
f282bb677188 drm/xe: Add function to check if BO has single placement
beac6e1551b9 drm/xe: Refactor default device atomic settings