From: Johan Hedberg <johan.hedberg@gmail.com>
To: Mikel Astiz <mikel.astiz.oss@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, claudio.takahasi@openbossa.org,
Mikel Astiz <mikel.astiz@bmw-carit.de>
Subject: Re: [PATCH v0 0/2] Media API clarifications
Date: Tue, 8 Jan 2013 13:57:32 +0200 [thread overview]
Message-ID: <20130108115732.GA8622@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1357638065-19156-1-git-send-email-mikel.astiz.oss@gmail.com>
Hi Mikel,
On Tue, Jan 08, 2013, Mikel Astiz wrote:
> The documentation of BlueZ 5.0 is lacking some details affecting the
> Media API, specially regarding the control of HFP/HSP volume.
>
> There is no known implementation of MediaTransport1 at this point so
> updating the documentation with two new optional properties could be
> in practice done without updating the interface suffix.
>
> Besides, the error codes returned by Acquire() and TryAcquire() are
> convenient to implement proper error logging in the client side.
>
> Mikel Astiz (2):
> media: Add HFP/HSP gains to transport API
> media: Clarify Acquire/TryAcquire error cases
>
> doc/media-api.txt | 32 +++++++++++++++++++++++++++++++-
> profiles/audio/transport.c | 2 +-
> 2 files changed, 32 insertions(+), 2 deletions(-)
Both patches have been applied. Thanks.
Johan
prev parent reply other threads:[~2013-01-08 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 9:41 [PATCH v0 0/2] Media API clarifications Mikel Astiz
2013-01-08 9:41 ` [PATCH v0 1/2] media: Add HFP/HSP gains to transport API Mikel Astiz
2013-01-08 9:41 ` [PATCH v0 2/2] media: Clarify Acquire/TryAcquire error cases Mikel Astiz
2013-01-08 11:57 ` Johan Hedberg [this message]
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=20130108115732.GA8622@x220.ger.corp.intel.com \
--to=johan.hedberg@gmail.com \
--cc=claudio.takahasi@openbossa.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mikel.astiz.oss@gmail.com \
--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