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

[Patchwork <patchwork@emeril.freedesktop.org>]

== Series Details ==

Series: series starting with [1/2] drm/xe/xe_guc_submit: Fix exec queue stop race condition
URL   : https://patchwork.freedesktop.org/series/131796/
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 0635fbec3ce5ae76fc2434836b9a082baaf3efb0
Author: Jonathan Cavitt <jonathan.cavitt@intel.com>
Date:   Thu Mar 28 14:33:58 2024 -0700

    drm/xe/xe_guc_status: Allow lr exec queues to be banned
    
    LR queues currently don't get banned during a GT/GuC reset because they
    lack a job.  Though they don't have a job to detect the reset status of,
    it's still possible to tell when they should be banned by looking at the
    LRC: if the LRC head and tail don't match, then the exec queue should be
    banned and cleaned up.
    
    This also requires swapping the usage of xe_sched_tdr_queue_imm with
    xe_guc_exec_queue_trigger_cleanup, as the former is specific to non-lr
    exec queues.
    
    Suggested-by: Matthew Brost <matthew.brost@intel.com>
    Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
+ /mt/dim checkpatch 98f893b726e1ba5db2680da3f9f53ab2af9780be drm-intel
c6d7bdb19db1 drm/xe/xe_guc_submit: Fix exec queue stop race condition
0635fbec3ce5 drm/xe/xe_guc_status: Allow lr exec queues to be banned