Re: [RFC v5 0/4] Optional acquire in Media API and related

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Mikel,

On Fri, Sep 14, 2012 at 3:55 PM, Mikel Astiz <mikel.astiz.oss@xxxxxxxxx> wrote:
> From: Mikel Astiz <mikel.astiz@xxxxxxxxxxxx>
>
> Same as v4 but rebased on the latest pushed patches.
>
> From original patch:
>
> This patch reopens the discussion started by the thread "when is acquire
> ok to call". The race condition seems to be real (even thought difficult
> to reproduce), and I couldn't think of any approach to solve this
> without altering the Media API.
>
> Mikel Astiz (4):
>   media: Split transport state based on playing flag
>   media: Expose transport state in D-Bus
>   media: Automatically release transport when HUP
>   media: Extend media API with optional acquire
>
>  audio/transport.c |  113 +++++++++++++++++++++++++++++++++++++++++++++++-----
>  doc/media-api.txt |   19 +++++++++
>  2 files changed, 121 insertions(+), 11 deletions(-)
>
> --
> 1.7.7.6

All 4 patches are now upstream, thanks.


-- 
Luiz Augusto von Dentz
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux