[Intel-xe] ✗ CI.checkpatch: warning for Frontbuffer tracking and dirtyfb (rev4)

[Patchwork]

== Series Details ==

Series: Frontbuffer tracking and dirtyfb (rev4)
URL   : https://patchwork.freedesktop.org/series/123751/
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
63c2b6b160bca2df6efc7bc4cea6f442097d7854
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit af1b07da4825d09370cc75f1f4b0746824248468
Author: Jouni Högander <jouni.hogander at intel.com>
Date:   Mon Oct 2 13:23:59 2023 +0300

    fixup! FIXME: drm/i915/display: Remaining changes to make xe compile
    
    Generic dirtyfb implementation which Xe is currently using is doing atomic
    commit which is inefficient. We have now dma fence handling in our dirtyfb
    implementation. This works with Xe and CPU/GPU frontbuffer rendering as
    long as sync objects are imported by userspace
    (dma_buf_import_sync_file). Switch to our custom dirtyfb implementation.
    
    Signed-off-by: Jouni Högander <jouni.hogander at intel.com>
+ /mt/dim checkpatch 13da205daec6272347232c2c523fe8cde8b67e35 drm-intel
fa1da69de drm/xe: Add empty def for i915_gem_object_flush_if_display
42ac5331d Revert "FIXME: drm/i915: More display ugly wa needed after rebase"
-:10: WARNING:UNKNOWN_COMMIT_ID: Unknown commit id '4bf10efdff69a34bfa55813593bfecbf6f5d6db9', maybe rebased or not pulled?
#10: 
This reverts commit 4bf10efdff69a34bfa55813593bfecbf6f5d6db9.

total: 0 errors, 1 warnings, 0 checks, 23 lines checked
2b8c96c4a drm/i915/display: Use intel_bo_to_drm_bo instead of obj->base
af1b07da4 fixup! FIXME: drm/i915/display: Remaining changes to make xe compile