From: "Hedberg Johan (Nokia-D/Helsinki)" <johan.hedberg@gmail.com>
To: Radoslaw Jablonski <ext-jablonski.radoslaw@nokia.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Additional handling incoming call indication for HS
Date: Wed, 14 Jul 2010 11:33:24 -0300 [thread overview]
Message-ID: <20100714143324.GA2939@jh-x301> (raw)
In-Reply-To: <1279116737-27025-1-git-send-email-ext-jablonski.radoslaw@nokia.com>
Hi,
On Wed, Jul 14, 2010, Radoslaw Jablonski wrote:
> Some headsets expect incoming call indication before they can send ATA
> command. In current implementation of telephony we do not send outband
> notyfication about incoming call when call previously was in WAITING state.
> And without that kind of notyfication BH-108 and BackBeat 903 headset cannot
> send ATA command - user is unable to answer to that call from headset.
>
> Added handling for that case in func handle_call_status(). When phone now is
> in CSD_CALL_STATUS_MT_ALERTING and previously was in CSD_CALL_STATUS_WAITING
> that means we need to send incoming call notyfication (it was not sent earlier
> because new call was waiting for end of active call). This will send RING
> commands to headset if it is needed.
> ---
> audio/telephony-maemo6.c | 15 ++++++++++++---
> 1 files changed, 12 insertions(+), 3 deletions(-)
Thanks for the patch. There are a few issues that'll need to be fixed
before pushing it upstream. The most serious one is this:
audio/telephony-maemo6.c: In function ‘handle_call_status’:
audio/telephony-maemo6.c:1007: error: comparison between signed and
unsigned integer expressions
Please always check compilation with ./bootstrap-configure since that'll
cause any warnings to show up as errors.
Another issue is the commit message width. Please keep it at a maximum
of 74 characters so that it's nicely viewable using git log on a
80-character wide terminal.
And then the following (minor) whitespace issue:
> + if(prev_status == CSD_CALL_STATUS_WAITING)
There should be a space between the if and the parenthesis. Otherwise
the patch was fine. So please fix these issues and resubmit. Thanks.
Johan
next prev parent reply other threads:[~2010-07-14 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 14:12 [PATCH] Additional handling incoming call indication for HS Radoslaw Jablonski
2010-07-14 14:33 ` Hedberg Johan (Nokia-D/Helsinki) [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-07-14 15:20 Radoslaw Jablonski
2010-07-14 17:08 ` Hedberg Johan (Nokia-D/Helsinki)
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=20100714143324.GA2939@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=ext-jablonski.radoslaw@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