✓ CI.checkpatch: success for drm/xe: Use USEC_PER_MSEC rather than the hard coding

[Patchwork]

== Series Details ==

Series: drm/xe: Use USEC_PER_MSEC rather than the hard coding
URL   : https://patchwork.freedesktop.org/series/131357/
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
a9eb1ac8298ef9f9146567c29fa762d8e9efa1ef
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 2821a2fe5fa29a56d7c1119750885e6cf15fa1d4
Author: Himal Prasad Ghimiray <himal.prasad.ghimiray at intel.com>
Date:   Wed Mar 20 14:03:25 2024 +0530

    drm/xe: Use USEC_PER_MSEC rather than the hard coding
    
    Use USEC_PER_MSEC rather than the hard coded value of 1000.
    
    Static analyzer Reported "casting either timeout_ms or
    1000U to type u64" to avoid overflow-before-widen.
    Using USEC_PER_MSEC seems better and will help with static analyzer
    report cleanup.
    
    Cc: Rodrigo Vivi <rodrigo.vivi at intel.com>
    Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray at intel.com>
+ /mt/dim checkpatch 67518d9ea0b8c4a01a4e304a0c71845bbabd0430 drm-intel
2821a2fe5fa2 drm/xe: Use USEC_PER_MSEC rather than the hard coding