✓ CI.checkpatch: success for drm/xe/guc: Drop error messages about missing GuC logs (rev2)

[Patchwork]

== Series Details ==

Series: drm/xe/guc: Drop error messages about missing GuC logs (rev2)
URL   : https://patchwork.freedesktop.org/series/143477/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit c161abbb900ec1f08cd6bea6e84facbefb240f9c
Author: John Harrison <John.C.Harrison at Intel.com>
Date:   Mon Jan 13 11:44:04 2025 -0800

    drm/xe/guc: Drop error messages about missing GuC logs
    
    The GuC log snapshot code would complain loudly if there was no GuC
    log to take a snapshot of or if the snapshot alloc failed. Originally,
    this code was only called on demand when a user (or developer)
    explicitly requested a dump of the log. Hence an error message was
    useful.
    
    However, it is now part of the general devcoredump file and is called
    for any GPU hang. Most people don't care about GuC logs and GPU hangs
    do not generally mean a kernel/GuC bug. More importantly, there are
    valid situations where there is no GuC log, e.g. SRIOV VFs.
    
    So drop the error message.
    
    Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/3958
    Signed-off-by: John Harrison <John.C.Harrison at Intel.com>
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch a45139b1e7578c7a4f1cbe8fae0943416a174136 drm-intel
c161abbb900e drm/xe/guc: Drop error messages about missing GuC logs