✓ CI.checkpatch: success for Cleaning up code related to VRAM regions and its initialization - part 2

[Patchwork]

== Series Details ==

Series: Cleaning up code related to VRAM regions and its initialization - part 2
URL   : https://patchwork.freedesktop.org/series/149503/
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
202708c00696422fd217223bb679a353a5936e23
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 3ac5e881852de8439ce01a771a3d030e3d246235
Author: Piotr Piórkowski <piotr.piorkowski at intel.com>
Date:   Mon May 26 16:56:47 2025 +0200

    drm/xe: Unify the initialization of VRAM regions
    
    Currently in the drivers we have defined VRAM regions per device and per
    tile. Initialization of these regions is done in two completely different
    ways. To simplify the logic of the code and make it easier to add new
    regions in the future, let's unify the way we initialize VRAM regions.
    
    Signed-off-by: Piotr Piórkowski <piotr.piorkowski at intel.com>
    Cc: Stuart Summers <stuart.summers at intel.com>
    Cc: Matthew Auld <matthew.auld at intel.com>
+ /mt/dim checkpatch 994b4d24e5526a8b1efca4ca25a3a3be47a886e5 drm-intel
f1c012960fa6 drm/xe: Use dynamic allocation for tile and device VRAM region structures
3ac5e881852d drm/xe: Unify the initialization of VRAM regions