✓ CI.checkpatch: success for drm/xe/vram: fix lpfn check

[Patchwork]

== Series Details ==

Series: drm/xe/vram: fix lpfn check
URL   : https://patchwork.freedesktop.org/series/141543/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit f67944111a86230f07acad655c5eba69f6730fa3
Author: Matthew Auld <matthew.auld at intel.com>
Date:   Tue Nov 19 10:19:27 2024 +0000

    drm/xe/vram: fix lpfn check
    
    Technically we should check the lfpn value and not the place->lpfn, for
    the case where the allocation itself could be as large as the entire
    region and not be range based, which might result in incorrectly doing a
    power-of-two roundup. The allocator itself will already ensure it's
    contiguous underneath for such an allocation. This shouldn't fix any
    current usecase, but never the less came up from some internal testing.
    
    Signed-off-by: Matthew Auld <matthew.auld at intel.com>
    Cc: Piotr Piórkowski <piotr.piorkowski at intel.com>
    Cc: Matthew Brost <matthew.brost at intel.com>
+ /mt/dim checkpatch 6af9eb4707b2f65024ac9412f3a9d76cc2516a9a drm-intel
f67944111a86 drm/xe/vram: fix lpfn check