✓ CI.checkpatch: success for drm/xe: Add locks in gtidle code (rev2)

[Patchwork]

== Series Details ==

Series: drm/xe: Add locks in gtidle code (rev2)
URL   : https://patchwork.freedesktop.org/series/143407/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit f38483b237fa08c80ada0a7df66cae1b0939f6de
Author: Vinay Belgaumkar <vinay.belgaumkar at intel.com>
Date:   Fri Jan 10 09:33:09 2025 -0800

    drm/xe: Add locks in gtidle code
    
    The update of the residency values needs to be protected by a lock to
    avoid multiple entrypoints, for example when multiple userspace clients
    read the sysfs file. Other in-kernel clients are going to be added to
    sample these values, making the problem worse. Protect those updates
    with a raw_spinlock so it can be called by future integration with perf
    pmu.
    
    Suggested-by: Lucas De Marchi <lucas.demarchi at intel.com>
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar at intel.com>
    Reviewed-by: Lucas De Marchi <lucas.demarchi at intel.com>
    Signed-off-by: Lucas De Marchi <lucas.demarchi at intel.com>
+ /mt/dim checkpatch 20058aae3e619821197cd32b736893f1d7917ba3 drm-intel
f38483b237fa drm/xe: Add locks in gtidle code