✓ CI.checkpatch: success for drm/xe/guc: Improve robustness of GuC log dumping to dmesg

[Patchwork]

== Series Details ==

Series: drm/xe/guc: Improve robustness of GuC log dumping to dmesg
URL   : https://patchwork.freedesktop.org/series/133109/
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
0daf0be5bb95eb0a0e42275e00a0e42d8d8fd543
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit aa70a894480df92a8a5c815ea790eeef2647e552
Author: John Harrison <John.C.Harrison at Intel.com>
Date:   Tue Apr 30 16:34:36 2024 -0700

    drm/xe/guc: Improve robustness of GuC log dumping to dmesg
    
    There is a debug mechanism for dumping the GuC log as an ASCII hex
    stream via dmesg. This is extremely useful for situations where it is
    not possibe to query the log from debugfs (self tests, bugs that cause
    the driver to fail to load, system hangs, etc.). However, dumping via
    dmesg is not the most reliable. The dmesg buffer is limited in size,
    can be rate limited and a simple hex stream is hard to parse by tools.
    
    So add extra information to the dump to make it more robust and
    parsable. This includes adding start and end tags to delimit the dump,
    using longer lines to reduce the per line overhead, adding a rolling
    count to check for missing lines and interleaved concurrent dumps and
    adding other important information such as the GuC version number and
    timestamp offset.
    
    Signed-off-by: John Harrison <John.C.Harrison at Intel.com>
+ /mt/dim checkpatch 3ac3efef3a1fc9d494b0a63c78bd0039a0b3d009 drm-intel
aa70a894480d drm/xe/guc: Improve robustness of GuC log dumping to dmesg