[Intel-xe] ✗ CI.checkpatch: warning for Documentation/gpu: Add a VM_BIND async document (rev5)

[Patchwork]

== Series Details ==

Series: Documentation/gpu: Add a VM_BIND async document (rev5)
URL   : https://patchwork.freedesktop.org/series/122457/
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
63c2b6b160bca2df6efc7bc4cea6f442097d7854
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 30ecffe451d0554398ad1ca672d44736668c29fc
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Thu Oct 12 15:25:52 2023 +0200

    Documentation/gpu: Add a VM_BIND async document
    
    Add a motivation for and description of asynchronous VM_BIND operation
    
    v2:
    - Fix typos (Nirmoy Das)
    - Improve the description of a memory fence (Oak Zeng)
    - Add a reference to the document in the Xe RFC.
    - Add pointers to sample uAPI suggestions
    v3:
    - Address review comments (Danilo Krummrich)
    - Formatting fixes
    v4:
    - Address typos (Francois Dugast)
    - Explain why in-fences are not allowed for VM_BIND operations for long-
      running workloads (Matthew Brost)
    v5:
    - More typo- and style fixing
    - Further clarify the implications of disallowing in-fences for VM_BIND
      operations for long-running workloads (Matthew Brost)
    v6:
    - Point out that a gpu_vm is a virtual GPU Address space.
      (Danilo Krummrich)
    - For an explanation of dma-fences point to the dma-fence documentation.
      (Paulo Zanoni)
    - Clarify that VM_BIND errors are reported synchronously. (Paulo Zanoni)
    - Use an rst doc reference when pointing to the async vm_bind document
      from the xe merge plan.
    - Add the VM_BIND documentation to the drm documentation table-of-content,
      using an intermediate "Misc DRM driver uAPI- and feature implementation
      guidelines"
    v7:
    - Update the error handling documentation to remove the VM error state.
    v8:
    - Clarify error handling and difference in operation support between
      async VM_BIND and sync VM_BIND. (Paulo Zanoni)
    - Update the sample uAPI with a self-contained example. (Paulo Zanoni)
    
    Cc: Paulo R Zanoni <paulo.r.zanoni at intel.com>
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Acked-by: Nirmoy Das <nirmoy.das at intel.com>
    Reviewed-by: Danilo Krummrich <dakr at redhat.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Reviewed-by: Paulo Zanoni <paulo.r.zanoni at intel.com>
+ /mt/dim checkpatch 6c0d1e36f310682297a5b07336b0883afc77f66e drm-intel
30ecffe45 Documentation/gpu: Add a VM_BIND async document
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'
-:54: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#54: 
new file mode 100644

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