✓ CI.checkpatch: success for drm/xe: Only allow 1 ufence per exec / bind IOCTL

[Patchwork]

== Series Details ==

Series: drm/xe: Only allow 1 ufence per exec / bind IOCTL
URL   : https://patchwork.freedesktop.org/series/129095/
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
e7f730565356938dd6c63cd498218fdc5d6a22b0
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 09e9af54c901d6b59a3667cbccb3ae55202b6992
Author: Matthew Brost <matthew.brost at intel.com>
Date:   Tue Jan 23 08:34:22 2024 -0800

    drm/xe: Only allow 1 ufence per exec / bind IOCTL
    
    The way exec ufences are coded only 1 ufence per IOCTL will be signaled.
    It is possible to fix this but for current use cases 1 ufence per IOCTL
    is sufficient. Enforce a limit of 1 ufence per IOCTL (both exec and bind
    to be uniform).
    
    Cc: Mika Kahola <mika.kahola at intel.com>
    Cc: Thomas Hellström <thomas.hellstrom at linux.intel.com>
    Signed-off-by: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch fc6b7c6ee7d786e6ed48425a2ce0e674906e4e5c drm-intel
09e9af54c drm/xe: Only allow 1 ufence per exec / bind IOCTL