✓ CI.checkpatch: success for drm/xe: Use separate rpm lockdep map for non-d3cold-capable devices

[Patchwork]

== Series Details ==

Series: drm/xe: Use separate rpm lockdep map for non-d3cold-capable devices
URL   : https://patchwork.freedesktop.org/series/137730/
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 a456725735ac29af020589bfcc036419c1f10854
Author: Thomas Hellström <thomas.hellstrom at linux.intel.com>
Date:   Fri Aug 23 18:58:17 2024 +0200

    drm/xe: Use separate rpm lockdep map for non-d3cold-capable devices
    
    For non-d3cold-capable devices we'd like to be able to wake up the
    device from reclaim. In particular, for Lunar Lake we'd like to be
    able to blit CCS metadata to system at shrink time; at least from
    kswapd where it's reasonable OK to wait for rpm resume and a
    preceding rpm suspend.
    
    Therefore use a separate lockdep map for such devices and prime it
    reclaim-tainted.
    
    v2:
    - Rename lockmap acquire- and release functions. (Rodrigo Vivi).
    - Reinstate the old xe_pm_runtime_lockdep_prime() function and
      rename it to xe_rpm_might_enter_cb(). (Matthew Auld).
    - Introduce a separate xe_pm_runtime_lockdep_prime function
      called from module init for known required locking orders.
    
    Cc: "Vivi, Rodrigo" <rodrigo.vivi at intel.com>
    Cc: "Auld, Matthew" <matthew.auld at intel.com>
    Signed-off-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Reviewed-by: Matthew Auld <matthew.auld at intel.com>
+ /mt/dim checkpatch 96041621daaf71059d790a2ddbaa60114371eada drm-intel
a456725735ac drm/xe: Use separate rpm lockdep map for non-d3cold-capable devices