✓ CI.checkpatch: success for drm/xe/guc: Escalate GuC load failure immediately (rev3)

[Patchwork]

== Series Details ==

Series: drm/xe/guc: Escalate GuC load failure immediately (rev3)
URL   : https://patchwork.freedesktop.org/series/144637/
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 fea7e1b44c71c80cbd4829ed00c0b2f12bfb0029
Author: Daniele Ceraolo Spurio <daniele.ceraolospurio at intel.com>
Date:   Thu Feb 13 13:39:01 2025 -0800

    drm/xe/guc: Escalate GuC load failure immediately
    
    When the Xe was first introduced, we intentionally avoided escalating
    GuC load failures, to not abort mid-probe. Xe is now mature enough and
    we gracefully handle probe failures, so we can start escalating
    immediately.
    
    Note that even without this patch the probe is still aborted because
    the attempt to enable CTs after GuC load will fail and that failure is
    already escalated.
    
    v2: only return success if the load_done variable is 1 (Tejas)
    
    Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: John Harrison <John.C.Harrison at Intel.com>
    Reviewed-by: Tejas Upadhyay <tejas.upadhyay at intel.com>
    Reviewed-by: John Harrison <John.C.Harrison at Intel.com>
    Reviewed-by: Satyanarayana K V P <satyanarayana.k.v.p at intel.com>
+ /mt/dim checkpatch 1fc9fc137d77154d162674c1648f148e29858725 drm-intel
fea7e1b44c71 drm/xe/guc: Escalate GuC load failure immediately