[Intel-xe] ✗ CI.checkpatch: warning for series starting with [1/2] drm/xe: Introduce a range-fence utility

[Patchwork]

== Series Details ==

Series: series starting with [1/2] drm/xe: Introduce a range-fence utility
URL   : https://patchwork.freedesktop.org/series/121018/
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
c7d32770e3cd31d9fc134ce41f329b10aa33ee15
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 3e774e49e01f26f661b95f6a50aaa44dfc623b92
Author: Matthew Brost <matthew.brost at intel.com>
Date:   Wed Jul 19 21:59:29 2023 -0700

    drm/xe: Make bind engines safe
    
    We currently have a race between bind engines which can result in
    corrupted page tables leading to faults.
    
    A simple example:
    bind A 0x0000-0x1000, engine A, has unsatisfied in-fence
    bind B 0x1000-0x2000, engine B, no in-fences
    exec A uses 0x1000-0x2000
    
    Bind B will pass bind A and exec A will fault. This occurs as bind A
    programs the root of the page table in a bind job which is held up by an
    in-fence. Bind B in this case just programs a leaf entry of the
    structure.
    
    To fix use range-fence utility to track cross bind engine conflicts. In
    the above example bind A would insert an dependency into the range-fence
    tree with a key of 0x0-0x7fffffffff, bind B would find that dependency
    and its bind job would scheduled behind the unsatisfied in-fence and
    bind A's job.
    
    Reviewed-by: Maarten Lankhorst<maarten.lankhorst at linux.intel.com>
    Co-developed-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Signed-off-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch f5459dca41d325590391d4512e937d8ffc2ce126 drm-intel
8a157c5f2 drm/xe: Introduce a range-fence utility
Traceback (most recent call last):
  File "scripts/spdxcheck.py", line 6, in <module>
    from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
Traceback (most recent call last):
  File "scripts/spdxcheck.py", line 6, in <module>
    from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
-:35: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#35: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 238 lines checked
3e774e49e drm/xe: Make bind engines safe
-:29: WARNING:BAD_SIGN_OFF: Co-developed-by and Signed-off-by: name/email do not match
#29: 
Co-developed-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Signed-off-by: Matthew Brost <matthew.brost at intel.com>

total: 0 errors, 1 warnings, 0 checks, 289 lines checked