✓ CI.checkpatch: success for drm/xe: Split MCR initialization

[Patchwork]

== Series Details ==

Series: drm/xe: Split MCR initialization
URL   : https://patchwork.freedesktop.org/series/134196/
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
51ce9f6cd981d42d7467409d7dbc559a450abc1e
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2026126c2af7e6162e56ed112cd7b70bb006fcd8
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Wed May 29 18:29:45 2024 +0200

    drm/xe: Split MCR initialization
    
    We can't follow the same initialization order of GT topology, MCR,
    PAT and GuC HWconfig, as done today on native/PF driver, on the VF
    driver, since fuse registers used in GT topology discovery will be
    obtained by the VF driver from the GuC.
    
    While we need to program the HW PAT table prior to loading the GuC,
    this requires only basic functionality of the MCR code, which could
    be done separately from the full MCR initialization that may need
    the GT topology.
    
    Split MCR initialization into two steps to avoid introducing VF
    specific code paths. This also fixes duplicated spin_lock inits.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Matt Roper <matthew.d.roper at intel.com>
    Cc: Michał Winiarski <michal.winiarski at intel.com>
    Cc: Zhanjun Dong <zhanjun.dong at intel.com>
+ /mt/dim checkpatch 04a18ea4732fe1473b708b39411684662aced11d drm-intel
2026126c2af7 drm/xe: Split MCR initialization