✓ CI.checkpatch: success for drm/xe/guc: Resend potentially lost H2G MMIO request

[Patchwork]

== Series Details ==

Series: drm/xe/guc: Resend potentially lost H2G MMIO request
URL   : https://patchwork.freedesktop.org/series/149575/
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
202708c00696422fd217223bb679a353a5936e23
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit d8e7422b8985620942b23061d4e23a4deda9758d
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Wed May 28 11:00:21 2025 +0200

    drm/xe/guc: Resend potentially lost H2G MMIO request
    
    There could be a scenario where the VF driver is resuming faster
    than the driver PF is able to complete the VF FLR sequence which
    includes reset of the VF scratch registers.  This may result in
    deletion of the ongoing HXG message (it could be either a host
    request or a GuC response).
    
    When we detect that HXG message was likey lost (scratch register
    with HXG header was zeroed) try to send this request once more
    before giving up.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Satyanarayana K V P <satyanarayana.k.v.p at intel.com>
+ /mt/dim checkpatch 87357770e16c3ee781dee93de25d175944f7d239 drm-intel
d8e7422b8985 drm/xe/guc: Resend potentially lost H2G MMIO request