✓ CI.checkpatch: success for drm/xe/xe_sync: initialise ufence.signalled

[Patchwork]

== Series Details ==

Series: drm/xe/xe_sync: initialise ufence.signalled
URL   : https://patchwork.freedesktop.org/series/139888/
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 63a8d9220102041e1ef99bcb4897ae4ddcff881f
Author: Matthew Auld <matthew.auld at intel.com>
Date:   Fri Oct 11 14:36:34 2024 +0100

    drm/xe/xe_sync: initialise ufence.signalled
    
    We can incorrectly think that the fence has signalled, if we get a
    non-zero value here from the kmalloc, which is quite plausible. Just use
    kzalloc to prevent stuff like this.
    
    Fixes: 977e5b82e090 ("drm/xe: Expose user fence from xe_sync_entry")
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
    Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
    Cc: Nirmoy Das <nirmoy.das at intel.com>
    Cc: <stable at vger.kernel.org> # v6.10+
    Reviewed-by: Nirmoy Das <nirmoy.das at intel.com>
+ /mt/dim checkpatch d2577be8b969257afb5f76964afc16ae4f6f7c07 drm-intel
63a8d9220102 drm/xe/xe_sync: initialise ufence.signalled