✓ CI.checkpatch: success for drm/xe: Fix missing runtime outer protection for ggtt_remove_node (rev2)

[Patchwork]

== Series Details ==

Series: drm/xe: Fix missing runtime outer protection for ggtt_remove_node (rev2)
URL   : https://patchwork.freedesktop.org/series/134308/
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
51ce9f6cd981d42d7467409d7dbc559a450abc1e
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit c6102ce810597d340f3a9396092c69bd07846e90
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date:   Fri May 31 15:53:15 2024 -0400

    drm/xe: Fix missing runtime outer protection for ggtt_remove_node
    
    Defer the ggtt node removal to a thread if runtime_pm is not active.
    
    The ggtt node removal can be called from multiple places, including
    places where we cannot protect with outer callers and places we are
    within other locks. So, try to grab the runtime reference if the
    device is already active, otherwise defer the removal to a separate
    thread from where we are sure we can wake the device up.
    
    v2: - use xe wq instead of system wq (Matt and CI)
        - Avoid GFP_KERNEL to be future proof since this removal can
        be called from outside our drivers and we don't want to block
        if atomic is needed. (Matt)
    
    Cc: Paulo Zanoni <paulo.r.zanoni at intel.com>
    Cc: Francois Dugast <francois.dugast at intel.com>
    Cc: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch 71fb583af6dea41793b38d947a991f06156f7f11 drm-intel
c6102ce81059 drm/xe: Fix missing runtime outer protection for ggtt_remove_node