[Intel-xe] ✗ CI.checkpatch: warning for drm/xe: nuke GuC on unload (rev4)

[Patchwork]

== Series Details ==

Series: drm/xe: nuke GuC on unload (rev4)
URL   : https://patchwork.freedesktop.org/series/122851/
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
e700ea2f248a75138759bcb443affeef4a2d1991
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 4a1cba436fad6f8bfd9adfdb6b761bf7a3e7c8cb
Author: Matthew Auld <matthew.auld at intel.com>
Date:   Thu Aug 24 17:04:45 2023 +0100

    drm/xe: nuke GuC on unload
    
    On PVC unloading followed by reloading the module often results in a
    completely dead machine (seems to be plaguing CI). Resetting the GuC
    like we do at load seems to cure it at least when locally testing this.
    
    v2:
      - Move pc_fini into guc_fini. We want to do the GuC reset just after
        calling pc_fini, otherwise we encounter communication failures. It
        also seems like a good idea to do the reset before we start releasing
        the various other GuC resources. In the case of pc_fini there is an
        explicit stop, but for other stuff like logs, ads, ctb there is not.
    
    References: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/542
    References: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/597
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch 72da4b45f58f2a95d45743801a10e1f1e1dcce05 drm-intel
/mt/dim: line 50: /root/.dimrc: No such file or directory