[Intel-xe] ✓ CI.checkpatch: success for User fence wait uAPI change to nanoseconds (rev4)

[Patchwork]

== Series Details ==

Series: User fence wait uAPI change to nanoseconds (rev4)
URL   : https://patchwork.freedesktop.org/series/119661/
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 d0e7046281b114275a7147c980e415455d53d42e
Author: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
Date:   Wed Jun 28 07:51:41 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 abdb420db479bae28a2abd7ba2c66229b7e8cb77 drm-intel
d0e704628 drm/xe: Use nanoseconds instead of jiffies in uapi for user fence