From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: Biren Pandya <birenpandya@gmail.com>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
laurent.pinchart@ideasonboard.com, sakari.ailus@linux.intel.com,
mchehab@kernel.org
Subject: Re: [PATCH v2 1/4] media: renesas: rcar-csi2: Add missing media_entity_cleanup()
Date: Mon, 22 Jun 2026 10:06:54 +0200 [thread overview]
Message-ID: <ajjsrRVdvV-tkr-i@zed> (raw)
In-Reply-To: <20260619121729.24899-5-birenpandya@gmail.com>
Hi Biren
On Fri, Jun 19, 2026 at 05:47:30PM +0530, Biren Pandya wrote:
> The probe error paths and remove function are missing calls to
> media_entity_cleanup(). Add them and introduce an err_entity label
> to ensure teardown logic properly inverses initialization.
>
> Signed-off-by: Biren Pandya <birenpandya@gmail.com>
Have you at least compiled this patch ?
../drivers/media/platform/renesas/rcar-csi2.c: In function ‘rcsi2_probe’:
../drivers/media/platform/renesas/rcar-csi2.c:2634:1: error: label ‘error_entity’ defined but not used [-Werror=unused-label]
2634 | error_entity:
| ^~~~~~~~~~~~
Also, don't send v(n+1) in reply to v(n). Each version of a series
goes in its own thread, with a proper cover letter and changelog.
I suggest to use b4.
> ---
> drivers/media/platform/renesas/rcar-csi2.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/media/platform/renesas/rcar-csi2.c b/drivers/media/platform/renesas/rcar-csi2.c
> index 7305cc4a04cb..61d7dfe14688 100644
> --- a/drivers/media/platform/renesas/rcar-csi2.c
> +++ b/drivers/media/platform/renesas/rcar-csi2.c
> @@ -2631,6 +2631,8 @@ static int rcsi2_probe(struct platform_device *pdev)
> v4l2_subdev_cleanup(&priv->subdev);
> error_pm_runtime:
> pm_runtime_disable(&pdev->dev);
> +error_entity:
> + media_entity_cleanup(&priv->subdev.entity);
> error_async:
> v4l2_async_nf_unregister(&priv->notifier);
> v4l2_async_nf_cleanup(&priv->notifier);
> @@ -2646,6 +2648,7 @@ static void rcsi2_remove(struct platform_device *pdev)
> v4l2_async_nf_cleanup(&priv->notifier);
> v4l2_async_unregister_subdev(&priv->subdev);
> v4l2_subdev_cleanup(&priv->subdev);
> + media_entity_cleanup(&priv->subdev.entity);
>
> pm_runtime_disable(&pdev->dev);
> }
> --
> 2.50.1 (Apple Git-155)
>
>
next prev parent reply other threads:[~2026-06-22 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 10:22 [PATCH 0/4] media: renesas: Add missing media_entity_cleanup() calls Biren Pandya
2026-06-19 10:22 ` [PATCH 1/4] media: renesas: rcar-csi2: Add missing media_entity_cleanup() Biren Pandya
2026-06-19 10:22 ` [PATCH 2/4] media: renesas: csisp: " Biren Pandya
2026-06-19 10:22 ` [PATCH 3/4] media: renesas: rcar-core: " Biren Pandya
2026-06-19 10:22 ` [PATCH 4/4] media: renesas: rzg2l-core: " Biren Pandya
2026-06-19 12:17 ` [PATCH v2 1/4] media: renesas: rcar-csi2: " Biren Pandya
2026-06-19 12:17 ` [PATCH v2 2/4] media: renesas: csisp: " Biren Pandya
2026-06-19 12:17 ` [PATCH v2 3/4] media: renesas: rcar-core: " Biren Pandya
2026-06-19 12:17 ` [PATCH v2 4/4] media: renesas: rzg2l-core: " Biren Pandya
2026-06-22 8:06 ` Jacopo Mondi [this message]
2026-06-22 11:57 ` [PATCH v2 1/4] media: renesas: rcar-csi2: " Laurent Pinchart
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=ajjsrRVdvV-tkr-i@zed \
--to=jacopo.mondi@ideasonboard.com \
--cc=birenpandya@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.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