✗ CI.checkpatch: warning for drm/xe/ufence: Flush xe ordered_wq in case of ufence timeout (rev2)

[Patchwork]

== Series Details ==

Series: drm/xe/ufence: Flush xe ordered_wq in case of ufence timeout (rev2)
URL   : https://patchwork.freedesktop.org/series/140386/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 26bd871db556b14abd07ed49de04cdb1e8e7a861
Author: Nirmoy Das <nirmoy.das at intel.com>
Date:   Thu Oct 24 17:18:15 2024 +0200

    drm/xe/ufence: Flush xe ordered_wq in case of ufence timeout
    
    Flush xe ordered_wq in case of ufence timeout which is observed
    on LNL and that points to the recent scheduling issue with E-cores.
    
    This is similar to the recent fix:
    commit e51527233804 ("drm/xe/guc/ct: Flush g2h worker in case of g2h
    response timeout") and should be removed once there is E core
    scheduling fix.
    
    v2: Add platform check(Himal)
        s/__flush_workqueue/flush_workqueue(Jani)
    
    Cc: Badal Nilawar <badal.nilawar at intel.com>
    Cc: Jani Nikula <jani.nikula at intel.com>
    Cc: Matthew Auld <matthew.auld at intel.com>
    Cc: John Harrison <John.C.Harrison at Intel.com>
    Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray at intel.com>
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Cc: <stable at vger.kernel.org> # v6.11+
    Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2754
    Suggested-by: Matthew Brost <matthew.brost at intel.com>
    Signed-off-by: Nirmoy Das <nirmoy.das at intel.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch 75eab7b9ee32a121d95a42ac704b679097f1fac4 drm-intel
26bd871db556 drm/xe/ufence: Flush xe ordered_wq in case of ufence timeout
-:60: WARNING:MISSING_FIXES_TAG: The commit message has 'stable@', perhaps it also needs a 'Fixes:' tag?

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