Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Syam Sidhardhan <s.syam@samsung.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Send the Extended Error result code, if requested in the failure cases
Date: Wed, 11 Jan 2012 18:42:46 +0200	[thread overview]
Message-ID: <20120111164246.GA10746@fusion.localdomain> (raw)
In-Reply-To: <1326297791-8533-1-git-send-email-s.syam@samsung.com>

Hi Syam,

On Wed, Jan 11, 2012, Syam Sidhardhan wrote:
> If HF has already requested for the Extended Error result code reporting,
> then send the same in certain failure cases. Earlier in this case we were
> sending normal Error.
> ---
>  audio/headset.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/audio/headset.c b/audio/headset.c
> index 6aef6a8..5455340 100644
> --- a/audio/headset.c
> +++ b/audio/headset.c
> @@ -1331,7 +1331,13 @@ static gboolean rfcomm_io_cb(GIOChannel *chan, GIOCondition cond,
>  		if (err == -EINVAL) {
>  			error("Badly formated or unrecognized command: %s",
>  					&slc->buf[slc->data_start]);
> -			err = headset_send(hs, "\r\nERROR\r\n");
> +
> +			if (slc->cme_enabled)
> +				err = headset_send(hs, "\r\n+CME ERROR: %d\r\n",
> +						CME_ERROR_NOT_SUPPORTED);
> +			else
> +				err = headset_send(hs, "\r\nERROR\r\n");
> +
>  			if (err < 0)
>  				goto failed;
>  		} else if (err < 0)

In this case it'd be easier to just do this:

	err = telephony_generic_rsp(device, CME_ERROR_NOT_SUPPORTED);

It'll do the cme_enabled check for you and send the right response
string.

Johan

  reply	other threads:[~2012-01-11 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 16:03 [PATCH] Send the Extended Error result code, if requested in the failure cases Syam Sidhardhan
2012-01-11 16:42 ` Johan Hedberg [this message]
2012-01-12 15:35   ` Syam Sidhardhan

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=20120111164246.GA10746@fusion.localdomain \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=s.syam@samsung.com \
    /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