✓ CI.checkpatch: success for PM notifier (rev3)

[Patchwork]

== Series Details ==

Series: PM notifier (rev3)
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 77539996f04942400c953c10d782518f47ef74e4
Author: Matthew Auld <matthew.auld at intel.com>
Date:   Wed Apr 16 16:09:17 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.
    
    v2 (Thomas):
      - Fix kernel doc and drop the pin as soon as we are done with the
        restore, instead of deferring to later.
    
    Suggested-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
    Reviewed-by: Thomas Hellström <thomas.hellstrom at linux.intel.com>
+ /mt/dim checkpatch ada794bd93930fd265c2df8f38196994173e1fde drm-intel
c452824bdcdf drm/xe: evict user memory in PM notifier
40bea5c45676 drm/xe: share bo dma-resv with backup object
77539996f049 drm/xe: handle pinned memory in PM notifier