✓ CI.checkpatch: success for drm/i915/dp: Correct max compressed bpp bounds by using link bpp (rev2)

[Patchwork]

== Series Details ==

Series: drm/i915/dp: Correct max compressed bpp bounds by using link bpp (rev2)
URL   : https://patchwork.freedesktop.org/series/143596/
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 85858157ff9e2cf068633e3ac5d445985552b171
Author: Ankit Nautiyal <ankit.k.nautiyal at intel.com>
Date:   Fri Jan 17 10:37:13 2025 +0530

    drm/i915/dp: Correct max compressed bpp bounds by using link bpp
    
    While setting the bounds for compressed bpp, we ensure that the
    compressed bpp is less than the pipe bpp.
    
    This causes an issue with the 420 output format, where the effective
    link bpp (or output bpp) is half that of the pipe bpp. Therefore instead
    of using pipe bpp, use the output bpp to set the bounds for the
    compressed bpp.
    
    v2: Use identifier output_bpp instead of link_bpp (Imre)
    
    Signed-off-by: Ankit Nautiyal <ankit.k.nautiyal at intel.com>
    Reviewed-by: Imre Deak <imre.deak at intel.com>
+ /mt/dim checkpatch d8c883b9b7702b39eb913a72fd7158ad9a6ea11f drm-intel
85858157ff9e drm/i915/dp: Correct max compressed bpp bounds by using link bpp