[Intel-xe] ✓ CI.Patch_applied: success for drm/i915: Initialize dkl_phy spin lock from display code path

[Patchwork]

== Series Details ==

Series: drm/i915: Initialize dkl_phy spin lock from display code path
URL   : https://patchwork.freedesktop.org/series/116326/
State : success

== Summary ==

=== Applying kernel patches on branch 'drm-xe-next' with base: ===
commit 9e9d9c1c2444672951809702f96f8257c367771a
Author:     Matthew Brost <matthew.brost at intel.com>
AuthorDate: Mon Apr 10 14:26:58 2023 -0700
Commit:     Matthew Brost <matthew.brost at intel.com>
CommitDate: Mon Apr 10 15:04:50 2023 -0700

    drm/xe: Don't grab runtime PM ref in engine create IOCTL
    
    A VM had a runtime PM ref, a engine can't be created without a VM, and
    the engine holds a ref to the VM thus this is unnecessary. Beyond that
    taking a ref in the engine create IOCTL and dropping it in the destroy
    IOCTL is wrong as a user doesn't have to call the destroy IOCTL (e.g.
    they can just kill the process or close the driver FD). If a user does
    this PM refs are leaked.
    
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Signed-off-by: Matthew Brost <matthew.brost at intel.com>
=== git am output follows ===
Applying: drm/i915: Initialize dkl_phy spin lock from display code path