✓ CI.checkpatch: success for drm/xe/mocs: Check that MOCS table.ops is assigned

[Patchwork]

== Series Details ==

Series: drm/xe/mocs: Check that MOCS table.ops is assigned
URL   : https://patchwork.freedesktop.org/series/135453/
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 bc9709d2360b5dc42c96a24ef48a70f58dc74d47
Author: Matt Roper <matthew.d.roper at intel.com>
Date:   Wed Jun 26 14:12:57 2024 -0700

    drm/xe/mocs: Check that MOCS table.ops is assigned
    
    When MOCS debugfs dumping was added in commit 9fbd0adbcbe8
    ("drm/xe/mocs: Add debugfs node to dump mocs"), a sanity check was added
    to xe_mocs_dump() to ensure table.ops->dump is not a NULL pointer.  The
    more common programmer mistake when adding MOCS enablement for new
    platforms is to simply forget to assign anything to table.ops
    altogether.  Extend the check to also cover a NULL table.ops and add a
    WARN() so that CI will help us catch these mistakes when new platforms
    are enabled in the future.
    
    Signed-off-by: Matt Roper <matthew.d.roper at intel.com>
+ /mt/dim checkpatch 6580bd2882edc6ea84200f2968d3d12b69b3ce40 drm-intel
bc9709d2360b drm/xe/mocs: Check that MOCS table.ops is assigned