From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Chuhong Yuan <hslester96@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Lubomir Rintel <lkundrak@v3.sk>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: marvell-ccic: Add missed v4l2_async_notifier_cleanup()
Date: Wed, 3 Jun 2020 15:41:43 +0300 [thread overview]
Message-ID: <20200603124143.GF16711@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20200603115605.1428636-1-hslester96@gmail.com>
Hi Chuhong,
Thanks for the patch.
On Wed, Jun 03, 2020 at 07:56:05PM +0800, Chuhong Yuan wrote:
> mccic_register() forgets to cleanup the notifier in its error handler.
> Add the missed call to fix it.
>
> Fixes: 3eefe36cc00c ("media: marvell-ccic: use async notifier to get the sensor")
> Signed-off-by: Chuhong Yuan <hslester96@gmail.com>
> ---
> drivers/media/platform/marvell-ccic/mcam-core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/media/platform/marvell-ccic/mcam-core.c b/drivers/media/platform/marvell-ccic/mcam-core.c
> index 09775b6624c6..cf2a0119e679 100644
> --- a/drivers/media/platform/marvell-ccic/mcam-core.c
> +++ b/drivers/media/platform/marvell-ccic/mcam-core.c
> @@ -1940,6 +1940,7 @@ int mccic_register(struct mcam_camera *cam)
> out:
> v4l2_async_notifier_unregister(&cam->notifier);
> v4l2_device_unregister(&cam->v4l2_dev);
> + v4l2_async_notifier_cleanup(&cam->notifier);
> return ret;
> }
> EXPORT_SYMBOL_GPL(mccic_register);
The same issue appears to be present in the mcam_shutdown(), could you fix
that one as well?
--
Regards,
Sakari Ailus
prev parent reply other threads:[~2020-06-03 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 11:56 [PATCH] media: marvell-ccic: Add missed v4l2_async_notifier_cleanup() Chuhong Yuan
2020-06-03 12:41 ` Sakari Ailus [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=20200603124143.GF16711@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=corbet@lwn.net \
--cc=hslester96@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkundrak@v3.sk \
--cc=mchehab@kernel.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;
as well as URLs for NNTP newsgroup(s).