✓ CI.checkpatch: success for Spin of Reduce GGTT display pinning latency.

[Patchwork]

== Series Details ==

Series: Spin of Reduce GGTT display pinning latency.
URL   : https://patchwork.freedesktop.org/series/130786/
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
7d6fb25447372de10c7d82d450bf95e4b2e2a0ab
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2c60c694d526f97717965267ec48b652aae9754b
Author: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
Date:   Tue Mar 5 21:20:02 2024 -0800

    drm/xe: Move xe_ggtt_invalidate out from ggtt->lock
    
    Considering the caller of the GGTT functions should keep the
    backing storage alive before the function completes, it's not
    necessary to invalidate with the GGTT lock held. This just adds
    latency for every user of the GGTT.
    
    Signed-off-by: Matthew Brost <matthew.brost at intel.com>
    Signed-off-by: Maarten Lankhorst <maarten.lankhorst at linux.intel.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch dd08fd912fdc1b72984a39852fdbee49b97b8ce4 drm-intel
4fe2100e4a80 drm/xe: Fix NULL check in xe_ggtt_init()
c8ed0295f52e drm/xe: Drop ggtt invalidate from display code
41524b1289b1 drm/xe: Add XE_BO_GGTT_INVALIDATE_BIT flag
2c60c694d526 drm/xe: Move xe_ggtt_invalidate out from ggtt->lock