From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: 'Dan Carpenter' <error27@gmail.com>
Cc: 'Mauro Carvalho Chehab' <mchehab@infradead.org>,
linux-media@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: RE: [patch] V4L/DVB: unlock on error path
Date: Thu, 19 Aug 2010 16:16:50 +0000 [thread overview]
Message-ID: <002801cb3fb9$ee00a370$ca01ea50$%nawrocki@samsung.com> (raw)
In-Reply-To: <20100812074158.GH645@bicker>
Thank you for catching this up. I had this fixed already, but due to hassle
caused by having multiple versions of the driver this bug somehow made it
unnoticed to mainline.
Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
> -----Original Message-----
> From: Dan Carpenter [mailto:error27@gmail.com]
> Sent: Thursday, August 12, 2010 9:42 AM
> To: Mauro Carvalho Chehab
> Cc: Pawel Osciak; Kyungmin Park; Sylwester Nawrocki; linux-
> media@vger.kernel.org; kernel-janitors@vger.kernel.org
> Subject: [patch] V4L/DVB: unlock on error path
>
> If we return directly here then we miss out on some mutex_unlock()s
>
> Signed-off-by: Dan Carpenter <error27@gmail.com>
>
> diff --git a/drivers/media/video/s5p-fimc/fimc-core.c
> b/drivers/media/video/s5p-fimc/fimc-core.c
> index b151c7b..1beb226 100644
> --- a/drivers/media/video/s5p-fimc/fimc-core.c
> +++ b/drivers/media/video/s5p-fimc/fimc-core.c
> @@ -822,7 +822,8 @@ static int fimc_m2m_s_fmt(struct file *file, void
> *priv, struct v4l2_format *f)
> } else {
> v4l2_err(&ctx->fimc_dev->m2m.v4l2_dev,
> "Wrong buffer/video queue type (%d)\n", f->type);
> - return -EINVAL;
> + ret = -EINVAL;
> + goto s_fmt_out;
> }
>
> pix = &f->fmt.pix;
prev parent reply other threads:[~2010-08-19 16:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 7:41 [patch] V4L/DVB: unlock on error path Dan Carpenter
2010-08-19 16:16 ` Sylwester Nawrocki [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='002801cb3fb9$ee00a370$ca01ea50$%nawrocki@samsung.com' \
--to=s.nawrocki@samsung.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.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