From: Sakari Ailus <sakari.ailus@iki.fi>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: mchehab@kernel.org,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] media: entity: Catch unbalanced media_pipeline_stop calls
Date: Sat, 6 May 2017 00:11:57 +0300 [thread overview]
Message-ID: <20170505211156.GI7456@valkosipuli.retiisi.org.uk> (raw)
In-Reply-To: <a89c9fa7-37e9-e857-268e-b4105c6c8e77@ideasonboard.com>
Hi Kieran / Mauro,
On Fri, May 05, 2017 at 06:33:22PM +0100, Kieran Bingham wrote:
> Hi Sakari,
>
> On 04/01/17 08:57, Sakari Ailus wrote:
> > Hi Kieran,
> >
> > Thanks for the patch!
> >
> > On Tue, Jan 03, 2017 at 05:05:58PM +0000, Kieran Bingham wrote:
> >> On 03/01/17 13:36, Laurent Pinchart wrote:
> >>> Hi Kieran,
> >>>
> >>> Thank you for the patch.
> >>>
> >>> On Tuesday 03 Jan 2017 13:12:11 Kieran Bingham wrote:
> >>>> Drivers must not perform unbalanced calls to stop the entity pipeline,
> >>>> however if they do they will fault in the core media code, as the
> >>>> entity->pipe will be set as NULL. We handle this gracefully in the core
> >>>> with a WARN for the developer.
> >>>>
> >>>> Replace the erroneous check on zero streaming counts, with a check on
> >>>> NULL pipe elements instead, as this is the symptom of unbalanced
> >>>> media_pipeline_stop calls.
> >>>>
> >>>> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> >>>
> >>> This looks good to me,
> >>>
> >>> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> >>>
> >>> I'll let Sakari review and merge the patch.
> >>
> >> Ahh, yes - I forgot to mention, although perhaps it will be obvious for
> >> Sakari - but this patch is based on top of Sakari's pending media
> >> pipeline and graph walk cleanup series :D
> >
> > I've applied this on top of the other patches.
> >
> > It's always good to mention dependencies to other patches, that's very
> > relevant for reviewers.
>
> I've just been going through my old branches doing some clean up - and I can't
> see that this patch [0] made it to integration anywhere.
>
> Did it get lost?
> It looks like the cleanup series it was based on made it through...
What I think happened was that I had applied it to the correct branch BUT I
already had sent a pull request on it. My apologies.
>
> Mauro, perhaps you could pick this one up now ?
The patchwork link is here:
<URL:https://patchwork.linuxtv.org/patch/38883/>
--
Regards,
Sakari Ailus
e-mail: sakari.ailus@iki.fi XMPP: sailus@retiisi.org.uk
next prev parent reply other threads:[~2017-05-05 21:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 13:12 [PATCH] media: entity: Catch unbalanced media_pipeline_stop calls Kieran Bingham
2017-01-03 13:36 ` Laurent Pinchart
2017-01-03 17:05 ` Kieran Bingham
2017-01-04 8:57 ` Sakari Ailus
2017-05-05 17:33 ` Kieran Bingham
2017-05-05 21:11 ` Sakari Ailus [this message]
2017-05-06 17:23 ` Kieran Bingham
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=20170505211156.GI7456@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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