linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Mariusz Skamra <mariusz.skamra@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/pts: Update RFCOMM test results
Date: Wed, 13 May 2015 16:46:50 +0200	[thread overview]
Message-ID: <19884146.Wkmg5IULTA@leonov> (raw)
In-Reply-To: <1431423262-31970-1-git-send-email-mariusz.skamra@tieto.com>

Hi Mariusz,

On Tuesday 12 of May 2015 11:34:22 Mariusz Skamra wrote:
> PTS 6.1 and Android 5.1
> ---
>  android/pics-rfcomm.txt  |  8 +++-----
>  android/pixit-rfcomm.txt |  2 +-
>  android/pts-rfcomm.txt   | 14 ++++++--------
>  3 files changed, 10 insertions(+), 14 deletions(-)
> 
> diff --git a/android/pics-rfcomm.txt b/android/pics-rfcomm.txt
> index 384f81d..032ee73 100644
> --- a/android/pics-rfcomm.txt
> +++ b/android/pics-rfcomm.txt
> @@ -1,6 +1,6 @@
>  RFCOMM PICS for the PTS tool.
> 
> -PTS version: 6.0
> +PTS version: 6.1
> 
>  * - different than PTS defaults
>  # - not yet implemented/supported
> @@ -25,7 +25,7 @@ Parameter Name		Selected	Description
>  ---------------------------------------------------------------------------
> ---- TSPC_RFCOMM_1_1		True (*)	Initialize RFCOMM Session (C.2)
>  TSPC_RFCOMM_1_2		True (*)	Respond to Initialization of an RFCOMM
> -					Session (C.2)
> +					Session (C.1)
>  TSPC_RFCOMM_1_3		True		Shutdown RFCOMM Session (M)
>  TSPC_RFCOMM_1_4		True		Respond to a Shutdown of an RFCOMM
>  					Session (M)
> @@ -49,13 +49,11 @@ TSPC_RFCOMM_1_20	True (*)	Send RPN Command (O)
>  TSPC_RFCOMM_1_21	True (*)	Closing Multiplexer by First Sending
>  					a DISC Command (O)
>  TSPC_RFCOMM_1_22	True		Support of Credit Based Flow Control (M)
> -TSPC_RFCOMM_1_23	True (*)	IUT Responds to Establishment of
> -					a DLC (C.1)
>  ---------------------------------------------------------------------------
> ---- C.1: Mandatory if SPP 1/2 (Device B) is supported, otherwise Excluded.
> C.2: Mandatory if SPP 1/1 (Device A) is supported, otherwise Excluded. C.3:
> Mandatory if SPP 1/1 (Device A) is supported, otherwise Optional. -C.4:
> Mandatory to support if 0/2 (RFCOMM 1.2) is supported, otherwise Optional.
> +C.4: Mandatory to support if TSPC_RFCOMM_0_2 is supported, otherwise
> Optional.
> ---------------------------------------------------------------------------
> ----
> 
> 
> diff --git a/android/pixit-rfcomm.txt b/android/pixit-rfcomm.txt
> index a3fbb27..88402a5 100644
> --- a/android/pixit-rfcomm.txt
> +++ b/android/pixit-rfcomm.txt
> @@ -1,6 +1,6 @@
>  RFCOMM PIXIT for the PTS tool.
> 
> -PTS version: 6.0
> +PTS version: 6.1
> 
>  * - different than PTS defaults
>  & - should be set to IUT Bluetooth address
> diff --git a/android/pts-rfcomm.txt b/android/pts-rfcomm.txt
> index e9b3f26..b1fce28 100644
> --- a/android/pts-rfcomm.txt
> +++ b/android/pts-rfcomm.txt
> @@ -1,9 +1,9 @@
>  PTS test results for RFCOMM
> 
> -PTS version: 6.0
> -Tested: 02-February-2015
> -Android version: 5.0
> -Kernel version: 3.19
> +PTS version: 6.1
> +Tested: 12-May-2015
> +Android version: 5.1
> +Kernel version: 4.1
> 
>  Results:
>  PASS	test passed
> @@ -32,9 +32,7 @@ TC_RFC_BV_14_C		N/A
>  TC_RFC_BV_15_C		PASS	rctest -r -P 1
>  TC_RFC_BV_17_C		PASS	rctest -d -P 1
>  TC_RFC_BV_19_C		PASS
> -TC_RFC_BV_21_C		PASS	PTS issue #13011
> -				rctest -w -N 10 -P 1
> -TC_RFC_BV_22_C		PASS	PTS issue #13011
> -				rctest -w -N 10 -P 1
> +TC_RFC_BV_21_C		PASS	rctest -w -N 10 -P 1
> +TC_RFC_BV_22_C		PASS	rctest -w -N 10 -P 1
>  TC_RFC_BV_25_C		PASS	rctest -r -P 1
>  ---------------------------------------------------------------------------
> ----

Applied, thanks.

-- 
BR
Szymon Janc

      reply	other threads:[~2015-05-13 14:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12  9:34 [PATCH] android/pts: Update RFCOMM test results Mariusz Skamra
2015-05-13 14:46 ` 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=19884146.Wkmg5IULTA@leonov \
    --to=szymon.janc@tieto.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=mariusz.skamra@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;
as well as URLs for NNTP newsgroup(s).