[Intel-xe] ✓ CI.checkpatch: success for series starting with [v2,1/4] drm/xe/guc: Fix wrong assert about full_len

[Patchwork]

== Series Details ==

Series: series starting with [v2,1/4] drm/xe/guc: Fix wrong assert about full_len
URL   : https://patchwork.freedesktop.org/series/126539/
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
63c2b6b160bca2df6efc7bc4cea6f442097d7854
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit b282b10aa1070c9d33059686ec3893443a7b2b2a
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Thu Nov 16 16:12:42 2023 +0100

    drm/xe/guc: Use valid scratch register for posting read
    
    There are only 4 scratch registers VF_SW_FLAG(0..3) on each GuC.
    We shouldn't use non-existing register VF_SW_FLAG(4) for posting
    read.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Reviewed-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch cb9b702d436952ddec33b020d549c7998cace9e2 drm-intel
6cd29910b drm/xe/guc: Fix wrong assert about full_len
ac7d6d826 drm/xe/guc: Copy response data from proper registers
b5b93b698 drm/xe/guc: Fix handling of GUC_HXG_TYPE_NO_RESPONSE_BUSY
b282b10aa drm/xe/guc: Use valid scratch register for posting read