✓ CI.checkpatch: success for drm/xe: Name and document Wa_14019789679

[Patchwork]

== Series Details ==

Series: drm/xe: Name and document Wa_14019789679
URL   : https://patchwork.freedesktop.org/series/137200/
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
9fe5037901cabbcdf27a6fe0dfb047ca1474d363
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 93570dd517f19d076211dd0700d9e33de7bd836b
Author: Matt Roper <matthew.d.roper at intel.com>
Date:   Mon Aug 12 11:10:43 2024 -0700

    drm/xe: Name and document Wa_14019789679
    
    Early in the development of Xe we identified an issue with SVG state
    handling on DG2 and MTL (and later on Xe2 as well).  In
    commit 72ac304769dd ("drm/xe: Emit SVG state on RCS during driver load
    on DG2 and MTL") and commit fb24b858a20d ("drm/xe/xe2: Update SVG state
    handling") we implemented our own workaround to prevent SVG state from
    leaking from context A to context B in cases where context B never
    issues a specific state setting.
    
    The hardware teams have now created official workaround Wa_14019789679
    to cover this issue.  The workaround description only requires emitting
    3DSTATE_MESH_CONTROL, since they believe that's the only SVG instruction
    that would potentially remain unset by a context B, but still cause
    notable issues if unwanted values were inherited from context A.
    However since we already have a more extensive implementation that emits
    the entire SVG state and prevents _any_ SVG state from unintentionally
    leaking, we'll stick with our existing implementation just to be safe.
    
    Signed-off-by: Matt Roper <matthew.d.roper at intel.com>
+ /mt/dim checkpatch 4f95bd933f4dacd22752bf8d6e548e8cc445d093 drm-intel
93570dd517f1 drm/xe: Name and document Wa_14019789679