[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <da9dcd58-41c1-089c-2061-be3bad6349a7@quicinc.com>
Date: Fri, 29 Mar 2024 11:39:11 -0700
From: Abhinav Kumar <quic_abhinavk@...cinc.com>
To: Miguel Ojeda <ojeda@...nel.org>, Rob Clark <robdclark@...il.com>,
Dmitry
Baryshkov <dmitry.baryshkov@...aro.org>
CC: Sean Paul <sean@...rly.run>,
Marijn Suijten
<marijn.suijten@...ainline.org>,
David Airlie <airlied@...il.com>, Daniel
Vetter <daniel@...ll.ch>,
Connor Abbott <cwabbott0@...il.com>, <linux-arm-msm@...r.kernel.org>,
<dri-devel@...ts.freedesktop.org>, <freedreno@...ts.freedesktop.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] drm/msm: fix the `CRASHDUMP_READ` target of
`a6xx_get_shader_block()`
On 3/26/2024 2:23 PM, Miguel Ojeda wrote:
> Clang 14 in an (essentially) defconfig arm64 build for next-20240326
> reports [1]:
>
> drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c:843:6: error:
> variable 'out' set but not used [-Werror,-Wunused-but-set-variable]
>
> The variable `out` in these functions is meant to compute the `target` of
> `CRASHDUMP_READ()`, but in this case only the initial value (`dumper->iova
> + A6XX_CD_DATA_OFFSET`) was being passed.
>
> Thus use `out` as it was intended by Connor [2].
>
> There was an alternative patch at [3] that removed the variable
> altogether, but that would only use the initial value.
>
> Fixes: 64d6255650d4 ("drm/msm: More fully implement devcoredump for a7xx")
> Closes: https://lore.kernel.org/lkml/CANiq72mjc5t4n25SQvYSrOEhxxpXYPZ4pPzneSJHEnc3qApu2Q@mail.gmail.com/ [1]
> Link: https://lore.kernel.org/lkml/CACu1E7HhCKMJd6fixZSPiNAz6ekoZnkMTHTcLFVmbZ-9VoLxKg@mail.gmail.com/ [2]
> Link: https://lore.kernel.org/lkml/20240307093727.1978126-1-colin.i.king@gmail.com/ [3]
> Signed-off-by: Miguel Ojeda <ojeda@...nel.org>
> ---
LGTM,
Reviewed-by: Abhinav Kumar <quic_abhinavk@...cinc.com>
Powered by blists - more mailing lists