From: Johan Hedberg <johan.hedberg@gmail.com>
To: Dmitriy Paliy <dmitriy.paliy@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] Fix +CLCC in maemo6 during CSD_CALL_STATUS_COMING
Date: Thu, 13 Oct 2011 13:46:35 +0300 [thread overview]
Message-ID: <20111013104635.GA19913@fusion.localdomain> (raw)
In-Reply-To: <1318501551-10048-1-git-send-email-dmitriy.paliy@nokia.com>
Hi Dmitriy,
On Thu, Oct 13, 2011, Dmitriy Paliy wrote:
> This fixes the same issue as in 8a6119ea1c685fc61419ee444a5967596f524c1c
> but for CSD_CALL_STATUS_COMING. Call status change sequence in csd is
> IDLE to COMING, COMING to PROCEEDING, and PROCEEDING to WAITING.
>
> Returned 'state of the call' value after CSD_CALL_STATUS_COMING, as well
> as after CSD_CALL_STATUS_PROCEEDING, in +CLCC shall be 5 (waiting, MT
> call) instead of 4 (incoming, MT call) in maemo6 telephony driver for the
> second incoming call.
> ---
> audio/telephony-maemo6.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2011-10-13 10:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 10:25 [PATCH BlueZ] Fix +CLCC in maemo6 during CSD_CALL_STATUS_COMING Dmitriy Paliy
2011-10-13 10:46 ` 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=20111013104635.GA19913@fusion.localdomain \
--to=johan.hedberg@gmail.com \
--cc=dmitriy.paliy@nokia.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).