✓ CI.checkpatch: success for drm/xe/pf: Move VFs reprovisioning to worker

[Patchwork]

== Series Details ==

Series: drm/xe/pf: Move VFs reprovisioning to worker
URL   : https://patchwork.freedesktop.org/series/143963/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit a1d4631f3c13a8e1de8f2fef45e32ce63bdd7dee
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Sat Jan 25 22:55:05 2025 +0100

    drm/xe/pf: Move VFs reprovisioning to worker
    
    Since the GuC is reset during GT reset, we need to re-send the
    entire SR-IOV provisioning configuration to the GuC. But since
    this whole configuration is protected by the PF master mutex and
    we can't avoid making allocations under this mutex (like during
    LMEM provisioning), we can't do this reprovisioning from gt-reset
    path if we want to be reclaim-safe. Move VFs reprovisioning to a
    async worker that we will start from the gt-reset path.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch b21557cf9ac310ed4c206f6661ac57fa090c42b2 drm-intel
a1d4631f3c13 drm/xe/pf: Move VFs reprovisioning to worker