✓ CI.checkpatch: success for Don't allocate managed BO for each policy change

[Patchwork]

== Series Details ==

Series: Don't allocate managed BO for each policy change
URL   : https://patchwork.freedesktop.org/series/148913/
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
202708c00696422fd217223bb679a353a5936e23
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 7715319cba0ccf5f2642be03019a96338716ce8c
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Tue May 13 00:00:18 2025 +0200

    drm/xe/guc: Don't allocate managed BO for each policy change
    
    We shouldn't use xe_managed_bo_create_from_data() to allocate
    temporary BO, as it will be released only on unload and every
    change in wedge_mode policy will consume resources (including
    precious GGTT). Instead just switchover to GuC buffer cache.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: John Harrison <John.C.Harrison at Intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch f28b1630b0e26e108cf5e2d9379bfed92dc4113f drm-intel
5221ff01cc49 drm/xe/guc: Unblock GuC buffer cache for all modes
7715319cba0c drm/xe/guc: Don't allocate managed BO for each policy change