✓ CI.checkpatch: success for drm/xe: Convert xe_pm_runtime_{get, put} to void and protect from recursion

[Patchwork]

== Series Details ==

Series: drm/xe: Convert xe_pm_runtime_{get, put} to void and protect from recursion
URL   : https://patchwork.freedesktop.org/series/130448/
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
9ab59fc4b7cb7663906ac4471a262434aef57f03
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 95751a942b229fc58e84d6ae5dd3a885b0d18257
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date:   Tue Feb 27 13:35:33 2024 -0500

    drm/xe: Convert xe_pm_runtime_{get, put} to void and protect from recursion
    
    With mem_access going away and pm_runtime getting called instead,
    we need to protect these against recursions.
    
    For D3cold, the TTM migration helpers will call for the job execution.
    Jobs execution will be protected by direct runtime_pm calls, but they
    cannot be called again if we are already at a runtime suspend/resume
    transaction when evicting/restoring memory for D3Cold. So, we will check
    for the xe_pm_read_callback_task.
    
    The put is asynchronous so there's no need to block it. However, for a
    proper balance, we need to ensure that the references are taken and
    restored regardless of the flow. So, let's convert them all to void and
    use some direct linux/pm_runtime functions.
    
    Cc: Matthew Auld <matthew.auld at intel.com>
    Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch 0d7a78693be62a8d1cd311376815b89b18de8204 drm-intel
95751a942b22 drm/xe: Convert xe_pm_runtime_{get, put} to void and protect from recursion