From: Mikel Astiz <mikel.astiz.oss@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: [RFC v5 0/4] Optional acquire in Media API and related
Date: Fri, 14 Sep 2012 14:55:56 +0200 [thread overview]
Message-ID: <1347627360-13997-1-git-send-email-mikel.astiz.oss@gmail.com> (raw)
From: Mikel Astiz <mikel.astiz@bmw-carit.de>
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
next reply other threads:[~2012-09-14 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 12:55 Mikel Astiz [this message]
2012-09-14 12:55 ` [RFC v5 1/4] media: Split transport state based on playing flag Mikel Astiz
2012-09-14 12:55 ` [RFC v5 2/4] media: Expose transport state in D-Bus Mikel Astiz
2012-09-14 12:55 ` [RFC v5 3/4] media: Automatically release transport when HUP Mikel Astiz
2012-09-14 12:56 ` [RFC v5 4/4] media: Extend media API with optional acquire Mikel Astiz
2012-09-17 13:33 ` [RFC v5 0/4] Optional acquire in Media API and related Luiz Augusto von Dentz
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=1347627360-13997-1-git-send-email-mikel.astiz.oss@gmail.com \
--to=mikel.astiz.oss@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz@bmw-carit.de \
/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