✓ CI.checkpatch: success for series starting with [01/12] drm/xe: Removed unused xe_ggtt_printk

[Patchwork]

== Series Details ==

Series: series starting with [01/12] drm/xe: Removed unused xe_ggtt_printk
URL   : https://patchwork.freedesktop.org/series/137398/
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 3d1c0d1e8188a1ff28a4a1ba92c58a5b34e2dda7
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date:   Fri Aug 16 11:02:43 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. (Brost)
    v3: amend forgot chunk declaring xe_device.
    v4: Use a xe_ggtt_region to encapsulate the node and remova info,
        wihtout the need for any memory allocation at runtime.
    v5: Actually fill the delayed_removal.invalidate (Brost)
    v6: - Ensure that ggtt_region is not freed before work finishes (Auld)
        - Own wq to ensures that the queued works are flushed before
          ggtt_fini (Brost)
    v7: also free ggtt_region on early !bound return (Auld)
    v8: Address the null deref (CI)
    v9: Based on the new xe_ggtt_node for the proper care of the lifetime
        of the object.
    v10: Redo the lost v5 change. (Brost)
    
    Cc: Matthew Auld <matthew.auld at intel.com>
    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 1f246caab12a2343f21ac227a26698e44a6490ff drm-intel
8fc79fcd9288 drm/xe: Removed unused xe_ggtt_printk
0b4a5719d01b drm/xe: Introduce GGTT documentation
380349575fd9 drm/xe: Remove unnecessary drm_mm.h includes
849c86d92ba3 drm/{i915, xe}: Avoid direct inspection of dpt_vma from outside dpt
8bb7a9baf447 drm/xe: Encapsulate drm_mm_node inside xe_ggtt_node
4d1b080abca8 drm/xe: Rename xe_ggtt_node related functions
c10860eb581b drm/xe: Limit drm_mm_node_allocated access to xe_ggtt_node
18c9f388645f drm/xe: Introduce xe_ggtt_largest_hole
2cb237015161 drm/xe: Introduce xe_ggtt_print_holes
49e5fbe135ec drm/xe: Rename xe_ggtt balloon functions to make the node clear
690b7b4b8775 drm/xe: Make xe_ggtt_node struct independent
3d1c0d1e8188 drm/xe: Fix missing runtime outer protection for ggtt_remove_node