✓ CI.checkpatch: success for series starting with [v2,1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition

[Patchwork]

== Series Details ==

Series: series starting with [v2,1/3] drm/xe/xe_guc_submit: Fix exec queue stop race condition
URL   : https://patchwork.freedesktop.org/series/132004/
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
10b531c2aeb176a1a539b4a77216232f97719cec
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit b06b36817d42466e77846aa9e0d1961713edde5f
Author: Jonathan Cavitt <jonathan.cavitt at intel.com>
Date:   Wed Apr 3 12:19:50 2024 -0700

    drm/xe/xe_guc_submit: Declare reset if banned or killed
    
    Add an additional condition to the reset_status guc_exec_queue_op that
    returns true if the exec queue has been banned or killed.  The
    reset_status op is only used for exiting any xe_wait_user_fence_ioctl
    that waits on an exec queue without timing out, so doing this will exit
    the ioctl early in cases where the exec queue can no longer function,
    such as after a GuC stop during a reset.
    
    Suggested-by: Matthew Brost <matthew.brost at intel.com>
    Signed-off-by: Jonathan Cavitt <jonathan.cavitt at intel.com>
+ /mt/dim checkpatch 406e10d886a22211d2866bfa9322aec1727171f8 drm-intel
10bef58ef480 drm/xe/xe_guc_submit: Fix exec queue stop race condition
a9f260c5c092 drm/xe/xe_guc_submit: Allow lr exec queues to be banned
b06b36817d42 drm/xe/xe_guc_submit: Declare reset if banned or killed