✓ CI.checkpatch: success for drm/i915: Give i915 and xe each their own display tracepoints

[Patchwork]

== Series Details ==

Series: drm/i915: Give i915 and xe each their own display tracepoints
URL   : https://patchwork.freedesktop.org/series/144006/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 766a3a4561e1c42a0e2edc9a60a976d909582e90
Author: Ville Syrjälä <ville.syrjala at linux.intel.com>
Date:   Mon Jan 27 23:30:55 2025 +0200

    drm/i915: Give i915 and xe each their own display tracepoints
    
    Currently we just define the display tracpoints with
    TRACE_SYSTEM i915. However the code gets included separately
    in i915 and xe, and now both modules are competing for the
    same tracpoints. Apparently whichever module is loaded first
    gets the tracepoints and the other guy is left with nothing.
    
    Give each module its own set of display tracpoints so that
    things work even when both modules are loaded.
    
    This one had me stumped for a bit when after a reboot I lost
    all i915 display tracpoints (on account of the new kernel
    also including xe, and something also ended up loading it
    before I manually loaded i915).
    
    Signed-off-by: Ville Syrjälä <ville.syrjala at linux.intel.com>
+ /mt/dim checkpatch 3de9463a46e57221df6a0b5f2f5b7f33207d76f7 drm-intel
766a3a4561e1 drm/i915: Give i915 and xe each their own display tracepoints