[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CADnq5_Pm0Vg-RNtnRoj1Dkc2Ke3paz1D6PeDkaKacGstBn7uVg@mail.gmail.com>
Date: Thu, 22 Aug 2024 14:34:00 -0400
From: Alex Deucher <alexdeucher@...il.com>
To: Yu Jiaoliang <yujiaoliang@...o.com>
Cc: Harry Wentland <harry.wentland@....com>, Leo Li <sunpeng.li@....com>,
Rodrigo Siqueira <Rodrigo.Siqueira@....com>, Xinhui Pan <Xinhui.Pan@....com>,
David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>,
Hamza Mahfooz <hamza.mahfooz@....com>, Alex Hung <alex.hung@....com>,
Dillon Varone <dillon.varone@....com>, amd-gfx@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org,
opensource.kernel@...o.com
Subject: Re: [PATCH v1 0/6] drm/amd/display: Use max/min macro
On Thu, Aug 22, 2024 at 2:57 AM Yu Jiaoliang <yujiaoliang@...o.com> wrote:
>
> *** BLURB HERE ***
>
> Yu Jiaoliang (6):
> drm/amd/display: Use max/min macro
> drm/amd/display: Use max/min macro
> drm/amd/display: Use max/min macro
> drm/amd/display: Use max/min macro
> drm/amd/display: Use max/min macro
> drm/amd/display: Use max/min macro
Is this the preferred kernel coding style for these type of
comparisons? Otherwise this just seems like a lot of churn for not
much gain.
Alex
>
> drivers/gpu/drm/amd/display/dc/bios/bios_parser.c | 4 ++--
> drivers/gpu/drm/amd/display/dc/clk_mgr/dcn20/dcn20_clk_mgr.c | 4 +++-
> drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 4 ++--
> drivers/gpu/drm/amd/display/dc/dc_dmub_srv.c | 2 +-
> drivers/gpu/drm/amd/display/dc/spl/dc_spl.c | 4 ++--
> drivers/gpu/drm/amd/display/modules/freesync/freesync.c | 4 ++--
> 6 files changed, 12 insertions(+), 10 deletions(-)
>
> --
> 2.34.1
>
Powered by blists - more mailing lists