✗ CI.checkpatch: warning for Expose raw access to GuC log over debugfs

[Patchwork]

== Series Details ==

Series: Expose raw access to GuC log over debugfs
URL   : https://patchwork.freedesktop.org/series/133507/
State : warning

== 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
57b97a66dd129aea93991dc66cd10477f7a05cf8
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 960772e41b97b843a9c751d554d726b4e3fdaa95
Author: Michal Wajdeczko <michal.wajdeczko at intel.com>
Date:   Sun May 12 17:36:06 2024 +0200

    drm/xe/guc: Expose raw access to GuC log over debugfs
    
    We already provide the content of the GuC log in debugsfs, but it
    is in a text format where each log dword is printed as hexadecimal
    number, which does not scale well with large GuC log buffers.
    
    To allow more efficient access to the GuC log, which could benefit
    our CI systems, expose raw binary log data.  In addition to less
    overhead in preparing text based GuC log file, the new GuC log file
    in binary format is also almost 3x smaller.
    
    Any existing script that expects the GuC log buffer in text format
    can use command like below to convert from new binary format:
    
            hexdump -e '4/4 "0x%08x " "\n"'
    
    but this shouldn't be the case as most decoders expect GuC log data
    in binary format.
    
    Signed-off-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Cc: John Harrison <John.C.Harrison at Intel.com>
+ /mt/dim checkpatch b5f09c51c3bb7cf14cac3e484880efdb405c098c drm-intel
21d464d2341c libfs: add simple_read_from_iomem()
-:43: WARNING:VOLATILE: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst
#43: FILE: fs/libfs.c:1060:
+			       const volatile void __iomem *from, size_t available)

-:88: WARNING:VOLATILE: Use of volatile is usually wrong: see Documentation/process/volatile-considered-harmful.rst
#88: FILE: include/linux/fs.h:3335:
+			       const volatile void __iomem *from, size_t available);

total: 0 errors, 2 warnings, 0 checks, 71 lines checked
eabc3808f97d iosys-map: add iosys_map_read_from() helper
959390d79169 drm/xe: Add wrapper for iosys_map_read_from
960772e41b97 drm/xe/guc: Expose raw access to GuC log over debugfs