✓ CI.checkpatch: success for series starting with [1/2] drm/xe/guc_pc: Do not stop probe or resume if GuC PC fails

[Patchwork]

== Series Details ==

Series: series starting with [1/2] drm/xe/guc_pc: Do not stop probe or resume if GuC PC fails
URL   : https://patchwork.freedesktop.org/series/144681/
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
22f9cda3436b4fe965b5c5f31d2f2c1bcb483189
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 7fa8ccd8d325f9ffabbf19a34676eb66829908db
Author: Rodrigo Vivi <rodrigo.vivi at intel.com>
Date:   Tue Feb 11 15:09:11 2025 -0500

    drm/xe/guc_pc: Remove duplicated pc_start call
    
    xe_guc_pc_start() was getting called from both
    xe_uc_init_hw() and from xe_guc_start().
    
    But both are called from do_gt_restart() and only
    xe_uc_init_hw() is called at initialization.
    
    So, let's remove the duplication in the regular gt_restart
    path.
    
    The only place where xe_guc_pc_start() won't get called now
    is on the gt_reset failure path. However, if gt_reset has
    failed, it is really unlikely that the PC start will work
    or is desired.
    
    Cc: Vinay Belgaumkar <vinay.belgaumkar at intel.com>
    Reviewed-by: Jonathan Cavitt <jonathan.cavitt at intel.com>
    Signed-off-by: Rodrigo Vivi <rodrigo.vivi at intel.com>
+ /mt/dim checkpatch e1c145994c41ed6dd5265bc0a7a276fe1834f3ee drm-intel
06fd7b7beb87 drm/xe/guc_pc: Do not stop probe or resume if GuC PC fails
7fa8ccd8d325 drm/xe/guc_pc: Remove duplicated pc_start call