✓ CI.checkpatch: success for drm/xe/guc: Treat non-response message after BUSY as unexpected

[Patchwork]

== Series Details ==

Series: drm/xe/guc: Treat non-response message after BUSY as unexpected
URL   : https://patchwork.freedesktop.org/series/128676/
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
faa12d3432d7ef7793d934cd9338c555e95a5aad
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 4122f11f9c1500de1048f813a6f1dfc56f7c2ade
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Thu Jan 11 16:48:38 2024 +0100

    drm/xe/guc: Treat non-response message after BUSY as unexpected
    
    Once GuC replied with GUC_HXG_TYPE_NO_RESPONSE_BUSY message then
    we may expect that only RESPONSE_SUCCESS or FAILURE message will
    be sent, anything else is a violation of the HXG protocol.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch 79184e72263e91528195db01783148435c7e4fad drm-intel
4122f11f9 drm/xe/guc: Treat non-response message after BUSY as unexpected