Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Sebastian Chlad <sebastian.chlad@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 1/2] android/pixit: Set phone number type
Date: Thu, 13 Mar 2014 15:24:59 +0100	[thread overview]
Message-ID: <2145617.JKP1Tthn4Q@uw000953> (raw)
In-Reply-To: <1394629949-13166-1-git-send-email-sebastian.chlad@tieto.com>

Hi Sebastian,

On Wednesday 12 of March 2014 14:12:28 Sebastian Chlad wrote:
> Phone number type should be set accordingly.
> ---
>  android/pixit-hfp.txt | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/android/pixit-hfp.txt b/android/pixit-hfp.txt
> index 3b04cbe..f539e07 100644
> --- a/android/pixit-hfp.txt
> +++ b/android/pixit-hfp.txt
> @@ -5,6 +5,7 @@ PTS version: 5.0
>  * - different than PTS defaults
>  & - should be set to IUT Bluetooth address
>  # - should be set to the respective phone numbers
> +^ - should be set according to the reported phone number's type
>  
>  		Required PIXIT settings
>  -------------------------------------------------------------------------------
> @@ -17,8 +18,8 @@ TSPX_ag_class_of_device					400204
>  TSPX_packet_type_sco					00A0
>  TSPX_phone_number					1234567 (#)
>  TSPX_second_phone_number				7654321 (#)
> -TSPX_phone_number_type					129
> -TSPX_second_phone_number_type				129
> +TSPX_phone_number_type					145 (*^)
> +TSPX_second_phone_number_type				145 (*^)
>  TSPX_phone_number_memory				1
>  TSPX_phone_number_memory_invalid_index			9999
>  TSPX_scan_all_memory_dial_locations			FALSE
> 

both patches applied, thanks.

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-03-13 14:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12 13:12 [PATCH 1/2] android/pixit: Set phone number type Sebastian Chlad
2014-03-12 13:12 ` [PATCH 2/2] android/pts: Add HFP PTS tests results Sebastian Chlad
2014-03-13 14:24 ` Szymon Janc [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=2145617.JKP1Tthn4Q@uw000953 \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=sebastian.chlad@tieto.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