Hi Hans,
On Mon, Jun 16, 2014 at 10:48 AM, Hans Verkuil wrote:
> Prabhakar,
>
> Are you going to make a pull request for this, or shall I take it? Should it
> be applied
> to 3.16?
>
As this is not a critical bug, I was planning to wait for v3.17 as
v3.16 is almost closed.
Regards,
--Prabhakar
Prabhakar,
Are you going to make a pull request for this, or shall I take it? Should it be
applied
to 3.16?
Regards,
Hans
On 06/13/2014 08:13 PM, Prabhakar Lad wrote:
> On Thu, Jun 12, 2014 at 8:01 AM, Dan Carpenter
> wrote:
>> We recently changed some locking around so we need some
On Thu, Jun 12, 2014 at 8:01 AM, Dan Carpenter wrote:
> We recently changed some locking around so we need some new unlocks on
> the error paths.
>
> Signed-off-by: Dan Carpenter
Applied!
Thanks,
--Prabhakar Lad
> ---
> v2: move the unlock so the list_for_each_entry_safe() loop is protected
>
We recently changed some locking around so we need some new unlocks on
the error paths.
Signed-off-by: Dan Carpenter
---
v2: move the unlock so the list_for_each_entry_safe() loop is protected
diff --git a/drivers/media/platform/davinci/vpif_capture.c
b/drivers/media/platform/davinci/vpif_captu
