From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Chen Zhongjin <chenzhongjin@huawei.com>,
<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<freedreno@lists.freedesktop.org>
Cc: <dianders@chromium.org>, <sean@poorly.run>,
<andersson@kernel.org>, <swboyd@chromium.org>,
<dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH -next] drm/msm: Remove unused variables 'top'
Date: Tue, 4 Oct 2022 09:27:56 -0700 [thread overview]
Message-ID: <fa74e1c0-53bb-4e73-4df5-c69cd455dd11@quicinc.com> (raw)
In-Reply-To: <20221010024010.2873633-1-chenzhongjin@huawei.com>
On 10/9/2022 7:40 PM, Chen Zhongjin wrote:
> 'commit 1e5df24b996c ("drm/msm/dpu: drop length from struct dpu_hw_blk_reg_map")'
> 'commit 9403f9a42c88 ("drm/msm/dpu: merge base_off with blk_off in struct dpu_hw_blk_reg_map")'
> These commits had merged hw.blk_off and hw.blk_off to mdp.
> So we don't need to get dpu_hw_mdp in dpu_kms_mdp_snapshot() now.
>
> Since there is no code using 'top' in this function. Remove it.
>
> Signed-off-by: Chen Zhongjin <chenzhongjin@huawei.com>
This has already been fixed with:
https://gitlab.freedesktop.org/drm/msm/-/commit/4bca876458caf7c105ab2ae9d80ff2cc9c60388d
> ---
> drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> index 008e1420e6e5..79e81f1443be 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c
> @@ -902,13 +902,9 @@ static void dpu_kms_mdp_snapshot(struct msm_disp_state *disp_state, struct msm_k
> int i;
> struct dpu_kms *dpu_kms;
> const struct dpu_mdss_cfg *cat;
> - struct dpu_hw_mdp *top;
>
> dpu_kms = to_dpu_kms(kms);
> -
> cat = dpu_kms->catalog;
> - top = dpu_kms->hw_mdp;
> -
> pm_runtime_get_sync(&dpu_kms->pdev->dev);
>
> /* dump CTL sub-blocks HW regs info */
prev parent reply other threads:[~2022-10-04 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 2:40 Chen Zhongjin
2022-10-04 16:27 ` Abhinav Kumar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa74e1c0-53bb-4e73-4df5-c69cd455dd11@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=andersson@kernel.org \
--cc=chenzhongjin@huawei.com \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean@poorly.run \
--cc=swboyd@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®