✓ CI.checkpatch: success for series starting with [1/2] drm/xe/mocs: Determine MCR separately for primary/media GT in kunit test

[Patchwork]

== Series Details ==

Series: series starting with [1/2] drm/xe/mocs: Determine MCR separately for primary/media GT in kunit test
URL   : https://patchwork.freedesktop.org/series/131151/
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
a9eb1ac8298ef9f9146567c29fa762d8e9efa1ef
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit e8621fee2d9ff1bf119f21e4bd23d7eee7d82976
Author: Matt Roper <matthew.d.roper at intel.com>
Date:   Thu Mar 14 12:58:27 2024 -0700

    drm/xe/mocs: Clarify which GT is being operated on
    
    Switch the MOCS-related debug messages to use a GT-specific logging
    function and add ID/type output to the beginning of the MOCS kunit test
    to assist with debug when problems arise.
    
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Signed-off-by: Matt Roper <matthew.d.roper at intel.com>
    Reviewed-by: Lucas De Marchi <lucas.demarchi at intel.com>
+ /mt/dim checkpatch c44e29a7b62293355744fd857aad93cbf43e5126 drm-intel
4fe471d54177 drm/xe/mocs: Determine MCR separately for primary/media GT in kunit test
e8621fee2d9f drm/xe/mocs: Clarify which GT is being operated on