✗ CI.checkpatch: warning for dma-fence: Fix sparse warnings due __rcu annotations

[Patchwork]

== Series Details ==

Series: dma-fence: Fix sparse warnings due __rcu annotations
URL   : https://patchwork.freedesktop.org/series/150338/
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
f8ff75ae1d2127635239b134695774ed4045d05b
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit e155c5dae42435ad7fbb50d05e8bcf7d99005e2f
Author: Tvrtko Ursulin <tvrtko.ursulin at igalia.com>
Date:   Mon Jun 16 16:59:52 2025 +0100

    dma-fence: Fix sparse warnings due __rcu annotations
    
    __rcu annotations on the return types from dma_fence_driver_name() and
    dma_fence_timeline_name() cause sparse to complain because both the
    constant signaled strings, and the strings return by the dma_fence_ops are
    not __rcu annotated.
    
    For a simple fix it is easiest to cast them with __rcu added and undo the
    smarts from the tracpoints side of things. There is no functional change
    since the rest is left in place. Later we can consider changing the
    dma_fence_ops return types too, and handle all the individual drivers
    which define them.
    
    Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin at igalia.com>
    Fixes: 506aa8b02a8d ("dma-fence: Add safe access helpers and document the rules")
    Reported-by: kernel test robot <lkp at intel.com>
    Closes: https://lore.kernel.org/oe-kbuild-all/202506162214.1eA69hLe-lkp@intel.com/
    Cc: Christian König <christian.koenig at amd.com>
+ /mt/dim checkpatch dea7240e83c9e58ec755a3d68e7db10068df6b76 drm-intel
e155c5dae424 dma-fence: Fix sparse warnings due __rcu annotations
-:4: WARNING:EMAIL_SUBJECT: A patch subject line should describe the change not the tool that found it
#4: 
Subject: [PATCH] dma-fence: Fix sparse warnings due __rcu annotations

-:93: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#93: FILE: include/trace/events/dma_fence.h:18:
+DECLARE_EVENT_CLASS(dma_fence,
 

-:102: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#102: FILE: include/trace/events/dma_fence.h:43:
+DEFINE_EVENT(dma_fence, dma_fence_emit,
 

-:110: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#110: FILE: include/trace/events/dma_fence.h:50:
+DEFINE_EVENT(dma_fence, dma_fence_init,
 

-:119: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#119: FILE: include/trace/events/dma_fence.h:64:
+DEFINE_EVENT(dma_fence, dma_fence_enable_signal,
 

-:127: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#127: FILE: include/trace/events/dma_fence.h:71:
+DEFINE_EVENT(dma_fence, dma_fence_signaled,
 

total: 0 errors, 1 warnings, 5 checks, 91 lines checked