[Intel-xe] ✓ CI.checkpatch: success for series starting with [1/3] drm/xe: Reformat xe_guc_regs.h

[Patchwork]

== Series Details ==

Series: series starting with [1/3] drm/xe: Reformat xe_guc_regs.h
URL   : https://patchwork.freedesktop.org/series/118808/
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
c7d32770e3cd31d9fc134ce41f329b10aa33ee15
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 71089db6effb17e98184d8c5b18b9f61556ae5ec
Author: Matt Roper <matthew.d.roper at intel.com>
Date:   Fri Jun 2 16:52:10 2023 -0700

    drm/xe: Don't hardcode GuC's MOCS index in register header
    
    Although PVC is currently the only platform that needs us to program a
    GuC register with the index of an uncached MOCS entry, it's likely other
    platforms will need this in the future.  Rather than hardcoding PVC's
    index into the register header, we should just pull the appropriate
    index from gt->mocs.uc_index to future-proof the code.
    
    Signed-off-by: Matt Roper <matthew.d.roper at intel.com>
+ /mt/dim checkpatch ef153c77d25ffd86b074190b77f9f561b9a5a909 drm-intel
d7ba1e4e4 drm/xe: Reformat xe_guc_regs.h
f0f85dc84 drm/xe: Initialize MOCS earlier
71089db6e drm/xe: Don't hardcode GuC's MOCS index in register header