[Intel-xe] ✓ CI.checkpatch: success for drm/xe: Use nanoseconds instead of jiffies in uapi for user fence (rev3)

[Patchwork]

== Series Details ==

Series: drm/xe: Use nanoseconds instead of jiffies in uapi for user fence (rev3)
URL   : https://patchwork.freedesktop.org/series/118670/
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
c7d32770e3cd31d9fc134ce41f329b10aa33ee15
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 9cd3474904d3fdddfd2c00cfe74b5a606321203a
Author: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
Date:   Fri Jun 16 07:37:27 2023 +0200

    drm/xe: Use nanoseconds instead of jiffies in uapi for user fence
    
    Using jiffies as a timeout from userspace is weird even it theoretically
    exists possiblity of acquiring jiffies via getconf. Unfortunately this
    method is unreliable and returned value may vary from configured in the
    kernel config.
    
    From now on 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 fence will expire at exact point of time.
    
    Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
    Cc: Andi Shyti <andi.shyti at linux.intel.com>
    Reviewed-by: Andi Shyti <andi.shyti at linux.intel.com>
+ /mt/dim checkpatch 293e40ed72cf5a9cf97438455bb8172fa260c7eb drm-intel
9cd347490 drm/xe: Use nanoseconds instead of jiffies in uapi for user fence