From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [v2,1/4] Bluetooth: Only allow setting msft_opcode at setup stage
Date: Tue, 12 Oct 2021 19:11:33 -0700 (PDT) [thread overview]
Message-ID: <61664055.1c69fb81.e9ee2.00d9@mx.google.com> (raw)
In-Reply-To: <20211013003055.2664728-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=562233
---Test result---
Test Summary:
CheckPatch PASS 6.63 seconds
GitLint PASS 3.63 seconds
BuildKernel PASS 613.81 seconds
TestRunner: Setup PASS 449.45 seconds
TestRunner: l2cap-tester PASS 10.26 seconds
TestRunner: bnep-tester PASS 5.53 seconds
TestRunner: mgmt-tester PASS 92.99 seconds
TestRunner: rfcomm-tester PASS 6.82 seconds
TestRunner: sco-tester PASS 7.06 seconds
TestRunner: smp-tester PASS 6.84 seconds
TestRunner: userchan-tester PASS 5.79 seconds
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 44357 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3564 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 646011 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11684 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 13924 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11830 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 6372 bytes --]
next prev parent reply other threads:[~2021-10-13 2:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 0:30 [PATCH v2 1/4] Bluetooth: Only allow setting msft_opcode at setup stage Luiz Augusto von Dentz
2021-10-13 0:30 ` [PATCH v2 2/4] Bluetooth: Only allow setting AOSP capable " Luiz Augusto von Dentz
2021-10-13 0:30 ` [PATCH v2 3/4] Bluetooth: vhci: Add support for setting msft_opcode Luiz Augusto von Dentz
2021-10-13 0:30 ` [PATCH v2 4/4] Bluetooth: vhci: Add support for setting aosp_capable Luiz Augusto von Dentz
2021-10-13 6:45 ` Marcel Holtmann
2021-10-13 21:29 ` Luiz Augusto von Dentz
2021-10-13 2:11 ` bluez.test.bot [this message]
2021-10-13 6:35 ` [PATCH v2 1/4] Bluetooth: Only allow setting msft_opcode at setup stage Marcel Holtmann
2021-10-13 21:10 ` Luiz Augusto von Dentz
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=61664055.1c69fb81.e9ee2.00d9@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.