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

[Patchwork]

== Series Details ==

Series: User fence wait uAPI change to nanoseconds (rev2)
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 e583018a10da07099db66f160d48dfe8e9842b8a
Author: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
Date:   Mon Jun 26 11:13:17 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.
    
    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 that the fence expires 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 76aec71c92f462efa45b365438a2c6f5417c2fec drm-intel
e583018a1 drm/xe: Use nanoseconds instead of jiffies in uapi for user fence