[Intel-xe] ✗ CI.checkpatch: warning for D3Cold Policy (rev2)

[Patchwork]

== Series Details ==

Series: D3Cold Policy (rev2)
URL   : https://patchwork.freedesktop.org/series/118035/
State : warning

== 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
c7d32770e3cd31d9fc134ce41f329b10aa33ee15
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 3568eb7a1155b6759c0473107f0c095a7195604e
Author: Anshuman Gupta <anshuman.gupta at intel.com>
Date:   Wed Jun 7 16:33:28 2023 +0530

    drm/xe/pm: Init pcode and restore vram on power lost
    
    Don't init pcode and restore VRAM objects in vain.
    We can rely on primary GT GUC_STATUS to detect whether
    card has really lost power even when d3cold is allowed by xe.
    Adding d3cold.lost_power flag to avoid pcode init and vram
    restoration.
    Also cleaning up the TODO code comment.
    
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Signed-off-by: Anshuman Gupta <anshuman.gupta at intel.com>
+ /mt/dim checkpatch 0f657f7b7f8886953ec1d946965a90fd286a6591 drm-intel
57fad5271 drm/xe/pm: Add pci d3cold_capable support
e4f6fe2f5 drm/xe/pm: Refactor xe_pm_runtime_init
ede55dbe1 drm/xe/pm: Add vram_d3cold_threshold Sysfs
Traceback (most recent call last):
  File "scripts/spdxcheck.py", line 6, in <module>
    from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
Traceback (most recent call last):
  File "scripts/spdxcheck.py", line 6, in <module>
    from ply import lex, yacc
ModuleNotFoundError: No module named 'ply'
-:32: WARNING:FILE_PATH_CHANGES: added, moved or deleted file(s), does MAINTAINERS need updating?
#32: 
new file mode 100644

total: 0 errors, 1 warnings, 0 checks, 243 lines checked
0c9d7b1d6 xe/drm/pm: Toggle d3cold_allowed using vram_usages
3568eb7a1 drm/xe/pm: Init pcode and restore vram on power lost