linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Ben Hutchings <ben.hutchings@codethink.co.uk>,
	linux-media@vger.kernel.org
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-kernel@codethink.co.uk,
	William Towle <william.towle@codethink.co.uk>,
	Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [RFC PATCH 0/5] media: rcar_vin: Fixes for buffer management
Date: Thu, 18 Dec 2014 20:36:24 +0300	[thread overview]
Message-ID: <54931098.30102@cogentembedded.com> (raw)
In-Reply-To: <1418914070.22813.13.camel@xylophone.i.decadent.org.uk>

Hello.

On 12/18/2014 05:47 PM, Ben Hutchings wrote:

> This is a re-submission of patches previously sent and archived at
> <http://thread.gmane.org/gmane.linux.ports.sh.devel/37184/>.  Will has
> rebased onto 3.18 and added a further patch to address Hans' review
> comments.

> The driver continues to works for single frame capture, and no longer
> provokes a WARNing.  However, video capture has regressed (a gstreamer
> capture pipeline yields a zero-length file).

> Ben.

> Ian Molton (4):
>    media: rcar_vin: Dont aggressively retire buffers
>    media: rcar_vin: Ensure all in-flight buffers are returned to error
>      state before stopping.
>    media: rcar_vin: Fix race condition terminating stream
>    media: rcar_vin: Clean up rcar_vin_irq

> William Towle (1):
>    media: rcar_vin: move buffer management to .stop_streaming handler

    Having actual fixes and clean-ups in a single series is not a good idea...

WBR, Sergei


  parent reply	other threads:[~2014-12-18 17:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 14:47 [RFC PATCH 0/5] media: rcar_vin: Fixes for buffer management Ben Hutchings
2014-12-18 14:49 ` [RFC PATCH 1/5] media: rcar_vin: Dont aggressively retire buffers Ben Hutchings
2015-01-18 20:16   ` Guennadi Liakhovetski
2014-12-18 14:49 ` [RFC PATCH 2/5] media: rcar_vin: Ensure all in-flight buffers are returned to error state before stopping Ben Hutchings
2014-12-30 13:14   ` Sakari Ailus
2014-12-18 14:49 ` [RFC PATCH 3/5] media: rcar_vin: Fix race condition terminating stream Ben Hutchings
2014-12-18 17:40   ` Sergei Shtylyov
2015-01-18 20:34     ` Guennadi Liakhovetski
2014-12-18 14:49 ` [RFC PATCH 4/5] media: rcar_vin: Clean up rcar_vin_irq Ben Hutchings
2014-12-18 14:50 ` [RFC PATCH 5/5] media: rcar_vin: move buffer management to .stop_streaming handler Ben Hutchings
2014-12-18 17:33   ` Sergei Shtylyov
2015-01-18 21:23   ` Guennadi Liakhovetski
2015-01-19 10:50     ` Ben Hutchings
2015-01-19 11:11       ` Guennadi Liakhovetski
2015-01-19 14:11         ` William Towle
2015-01-19 14:25           ` Guennadi Liakhovetski
2015-01-20 12:27             ` William Towle
2015-01-19 14:52           ` Hans Verkuil
2014-12-18 17:36 ` Sergei Shtylyov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-16 16:22 [RFC PATCH 0/5] media: rcar_vin: Fixes for buffer management William Towle

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=54931098.30102@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-kernel@codethink.co.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=william.towle@codethink.co.uk \
    /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).