✓ CI.checkpatch: success for PM notifier

[Patchwork]

== Series Details ==

Series: PM notifier
URL   : https://patchwork.freedesktop.org/series/147536/
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
13a92ce9fd458ebd6064f23cec8c39c53d02ed26
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2d9b85f4743463237eb828b5c9e348ec1c48de3d
Author: Matthew Auld <matthew.auld at intel.com>
Date:   Thu Apr 10 17:20:20 2025 +0100

    drm/xe: handle pinned memory in PM notifier
    
    Userspace is still alive and kicking at this point so actually moving
    pinned stuff here is tricky. However, we can instead pre-allocate the
    backup storage upfront from the notifier, such that we scoop up as much
    as we can, and then leave the final .suspend() to do the actual copy (or
    allocate anything that we missed). That way the bulk of our allocations
    will hopefully be done outside the more restrictive .suspend().
    
    We do need to be extra careful though, since the pinned handling can now
    race with PM notifier, like something becoming unpinned after we prepare
    it from the notifier.
    
    Suggested-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
+ /mt/dim checkpatch 457049ad31ee5b64dd86230518144d366c32bc04 drm-intel
4b3fa2938a09 drm/xe: evict user memory in PM notifier
224948fd9369 drm/xe: share bo dma-resv with backup object
2d9b85f47434 drm/xe: handle pinned memory in PM notifier