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 test notes for L2CAP
Date: Fri, 13 Feb 2015 12:50:36 +0100 [thread overview]
Message-ID: <2736230.pMgGvnRDOI@uw000953> (raw)
In-Reply-To: <1423745562-15295-1-git-send-email-mariusz.skamra@tieto.com>
Hi Mariusz,
On Thursday 12 of February 2015 13:52:42 Mariusz Skamra wrote:
> Daemon should be stopped for test purposes.
> ---
> android/pts-l2cap.txt | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/android/pts-l2cap.txt b/android/pts-l2cap.txt
> index b5fdb05..b625861 100644
> --- a/android/pts-l2cap.txt
> +++ b/android/pts-l2cap.txt
> @@ -14,6 +14,8 @@ N/A test is disabled due to PICS setup
> -------------------------------------------------------------------------------
> Test Name Result Notes
> -------------------------------------------------------------------------------
> + For all tests daemon should be stopped then:
> + setprop ctl.start hciattach
> TC_COS_CED_BV_01_C PASS l2test -n -P 4113 <bdaddr>
> TC_COS_CED_BV_03_C PASS l2test -y -N 1 -P 4113 <bdaddr>
> TC_COS_CED_BV_04_C PASS l2test -n -P 4113 <bdaddr>
> @@ -151,9 +153,6 @@ TC_ECF_BV_05_C N/A
> TC_ECF_BV_06_C N/A
> TC_ECF_BV_07_C N/A
> TC_ECF_BV_08_C N/A
> - NOTE: for LE tests daemon should be stopped
> - then:
> - setprop ctl.start hciattach
> TC_LE_CPU_BV_01_C PASS l2test -n -V le_public -J 4
> TC_LE_CPU_BV_02_C PASS l2test -n -V le_public -J 4 <braddr>
> TC_LE_CPU_BI_01_C PASS l2test -n -V le_public -J 4 <braddr>
Applied, thanks.
--
Best regards,
Szymon Janc
prev parent reply other threads:[~2015-02-13 11:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 12:52 [PATCH] android/pts: Update test notes for L2CAP Mariusz Skamra
2015-02-13 11:50 ` 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=2736230.pMgGvnRDOI@uw000953 \
--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).