[Intel-xe] ✗ CI.checkpatch: warning for User fence wait uAPI change to nanoseconds (rev3)

[Patchwork]

== Series Details ==

Series: User fence wait uAPI change to nanoseconds (rev3)
URL   : https://patchwork.freedesktop.org/series/119661/
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
c7d32770e3cd31d9fc134ce41f329b10aa33ee15
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2dcc7b01b2ed618af29d3c54fa962bcb3aed735c
Author: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
Date:   Tue Jun 27 19:16:26 2023 +0200

    drm/xe: Use nanoseconds instead of jiffies in uapi for user fence
    
    Using jiffies as a timeout from userspace is weird even if
    theoretically exists possiblity of acquiring jiffies via getconf.
    Unfortunately this method is unreliable and the returned
    value may vary from the one configured in the kernel config.
    
    Now timeout is expressed in nanoseconds and its interpretation depends
    on setting DRM_XE_UFENCE_WAIT_ABSTIME flag. Relative timeout (flag
    is not set) means fence expire at now() + timeout. Absolute timeout
    (flag is set) means that the fence expires at exact point of time.
    Passing negative timeout means we will wait "forever" by setting
    wait time to MAX_SCHEDULE_TIMEOUT.
    
    Cc: Andi Shyti <andi.shyti at linux.intel.com>
    Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
+ /mt/dim checkpatch d06a7e92d9a63597656367b287824d4eaff581bc drm-intel
2dcc7b01b drm/xe: Use nanoseconds instead of jiffies in uapi for user fence
-:83: CHECK:MULTIPLE_ASSIGNMENTS: multiple assignments should be avoided
#83: FILE: drivers/gpu/drm/xe/xe_wait_user_fence.c:176:
+		timeout = args->timeout = MAX_SCHEDULE_TIMEOUT;

total: 0 errors, 0 warnings, 1 checks, 102 lines checked