From: Szymon Janc <szymon.janc@gmail.com>
To: Jakub Tyszkowski <jakub.tyszkowski@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 3/3] android/ipc: Add PTS test results document for AVCTP
Date: Fri, 17 Jan 2014 21:34:27 +0100 [thread overview]
Message-ID: <1954110.rF3TraP8Zh@athlon> (raw)
In-Reply-To: <1389866462-7993-3-git-send-email-jakub.tyszkowski@tieto.com>
Hi Jakub,
On Thursday 16 January 2014 11:01:02 Jakub Tyszkowski wrote:
> This will allow for better tracking of current state of implementation.
> ---
> android/Makefile.am | 1 +
> android/pts-avctp.txt | 41 +++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 42 insertions(+)
> create mode 100644 android/pts-avctp.txt
>
Please fix commit title prefix android/ipc -> android/pts
> diff --git a/android/Makefile.am b/android/Makefile.am
> index 95ed7a7..f030bd4 100644
> --- a/android/Makefile.am
> +++ b/android/Makefile.am
> @@ -149,5 +149,6 @@ EXTRA_DIST += android/Android.mk android/hal-ipc-api.txt
> android/README \ android/pics-a2dp.txt android/pixit-a2dp.txt \
> android/pics-avctp.txt android/pixit-avctp.txt \
> android/pts-a2dp.txt android/pts-avrcp.txt \
> + android/pts-avctp.txt \
>
> android/pts-l2cap.txt
> diff --git a/android/pts-avctp.txt b/android/pts-avctp.txt
> new file mode 100644
> index 0000000..c057a10
> --- /dev/null
> +++ b/android/pts-avctp.txt
> @@ -0,0 +1,41 @@
> +PTS test results for AVCTP
> +
> +PTS version: 5.0
> +Tested: --not yet tested--
> +
> +Results:
> +PASS test passed
> +FAIL test failed
> +INC test is inconclusive
> +N/A test is disabled due to PICS setup
> +
> + Controller (CT)
> +---------------------------------------------------------------------------
> ---- +Test Name Result Notes
> +---------------------------------------------------------------------------
> ---- +TC_CT_CCM_BV_01_C N/A
> +TC_CT_CCM_BV_02_C N/A
> +TC_CT_CCM_BV_03_C N/A
> +TC_CT_CCM_BV_04_C N/A
> +TC_CT_CCM_BI_01_C N/A
> +TC_CT_NFR_BV_01_C N/A
> +TC_CT_NFR_BV_04_C N/A
> +TC_CT_FRA_BV_01_C N/A
> +TC_CT_FRA_BV_04_C N/A
> +---------------------------------------------------------------------------
> ---- +
> +
> + Target (TG)
> +---------------------------------------------------------------------------
> ---- +Test Name Result Notes
> +---------------------------------------------------------------------------
> ---- +TC_TG_CCM_BV_01_C INC
> +TC_TG_CCM_BV_02_C INC
> +TC_TG_CCM_BV_03_C INC
> +TC_TG_CCM_BV_04_C INC
> +TC_TG_NFR_BV_02_C INC
> +TC_TG_NFR_BV_03_C INC
> +TC_TG_NFR_BI_01_C INC
> +TC_TG_FRA_BV_02_C INC
> +TC_TG_FRA_BV_03_C INC
> +---------------------------------------------------------------------------
> ----
--
Szymon K. Janc
szymon.janc@gmail.com
next prev parent reply other threads:[~2014-01-17 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 10:01 [PATCH 1/3] android/pts: Add PTS test results document for A2DP Jakub Tyszkowski
2014-01-16 10:01 ` [PATCH 2/3] android/pts: Add PTS test results document for AVRCP Jakub Tyszkowski
2014-01-16 10:01 ` [PATCH 3/3] android/ipc: Add PTS test results document for AVCTP Jakub Tyszkowski
2014-01-17 20:34 ` Szymon Janc [this message]
2014-01-17 20:31 ` [PATCH 1/3] android/pts: Add PTS test results document for A2DP Szymon Janc
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=1954110.rF3TraP8Zh@athlon \
--to=szymon.janc@gmail.com \
--cc=jakub.tyszkowski@tieto.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).