✓ CI.checkpatch: success for series starting with [1/2] drm/xe: Assert pat.ops function pointers

[Patchwork]

== Series Details ==

Series: series starting with [1/2] drm/xe: Assert pat.ops function pointers
URL   : https://patchwork.freedesktop.org/series/132205/
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
10b531c2aeb176a1a539b4a77216232f97719cec
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 1abc4b2caf37faf09ebd323c0f8a7a992f27a231
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Tue Apr 9 12:51:06 2024 +0200

    drm/xe: Check pat.ops before dumping PAT settings
    
    We may leave pat.ops unset when running on brand new platform or
    when running as a VF.  While the former is unlikely, the latter
    is valid (future) use case and will cause NPD when someone will
    try to dump PAT settings by debugfs.
    
    It's better to check pointer to pat.ops instead of specific .dump
    hook, as we have this hook always defined for every .ops variant.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
+ /mt/dim checkpatch eea58bf00b72f3fd0abdf5fb144f988c23056b8d drm-intel
f84ff5ded976 drm/xe: Assert pat.ops function pointers
1abc4b2caf37 drm/xe: Check pat.ops before dumping PAT settings