From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: sunran001@208suo.com, robdclark@gmail.com,
quic_abhinavk@quicinc.com, airlied@gmail.com, daniel@ffwll.ch
Cc: linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/msm/dsi: add missing put_device()
Date: Tue, 18 Jul 2023 11:35:16 +0300 [thread overview]
Message-ID: <c2d21b04-d400-83ec-9e63-87f570c5cfd8@linaro.org> (raw)
In-Reply-To: <225e67f32dbc423daa4a83bc0c4f2179@208suo.com>
On 18/07/2023 11:33, sunran001@208suo.com wrote:
> The of_find_device_by_node() takes a reference to the underlying device
> structure, we should release that reference.
>
> Detected by coccinelle with the following ERROR:
> ./drivers/gpu/drm/msm/dsi/dsi.c:50:1-7: ERROR: missing put_device; call
> of_find_device_by_node on line 32, but without a corresponding object
> release within this function.
Still NAK, the device should not be put. It is handled in dsi_destroy(),
as I wrote in the previous email. Please stop.
Note, your patch lacks versioning and changelog. Please care to read
Documentation/process/submitting-patches.rst before sending your changes.
>
> Signed-off-by: Ran Sun <sunran001@208suo.com>
> ---
> drivers/gpu/drm/msm/dsi/dsi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/msm/dsi/dsi.c b/drivers/gpu/drm/msm/dsi/dsi.c
> index 81461e8852a7..5e3cc287f0d3 100644
> --- a/drivers/gpu/drm/msm/dsi/dsi.c
> +++ b/drivers/gpu/drm/msm/dsi/dsi.c
> @@ -46,7 +46,7 @@ static int dsi_get_phy(struct msm_dsi *msm_dsi)
> DRM_DEV_ERROR(&pdev->dev, "%s: phy driver is not ready\n",
> __func__);
> return -EPROBE_DEFER;
> }
> - put_device(&pdev->dev);
> + put_device(&phy_pdev->dev);
> return 0;
> }
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-07-18 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230718083149.17178-1-xujianghui@cdjrlc.com>
2023-07-18 8:33 ` sunran001
2023-07-18 8:35 ` Dmitry Baryshkov [this message]
[not found] <20230718081139.16918-1-xujianghui@cdjrlc.com>
2023-07-18 8:13 ` sunran001
2023-07-18 8:15 ` Dmitry Baryshkov
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=c2d21b04-d400-83ec-9e63-87f570c5cfd8@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--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=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=sunran001@208suo.com \
/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®