From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, apusaka@google.com
Subject: RE: MSFT offloading support for advertisement monitor
Date: Tue, 22 Dec 2020 03:20:33 -0800 (PST) [thread overview]
Message-ID: <5fe1d681.1c69fb81.ff497.227e@mx.google.com> (raw)
In-Reply-To: <20201222182553.v5.1.I92d2e2a87419730d60136680cbe27636baf94b15@changeid>
[-- Attachment #1: Type: text/plain, Size: 2878 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=405241
---Test result---
##############################
Test: CheckPatch - PASS
##############################
Test: CheckGitLint - FAIL
workflow: Add workflow files for ci
1: T1 Title exceeds max length (92>72): "Merge 241e46f9ac97998615100fe05bfbea104d600b6e into b52183867829c8e58ccfb3e3485cb4b55ec1bd20"
3: B6 Body message is missing
Bluetooth: advmon offload MSFT add rssi support
1: T1 Title exceeds max length (92>72): "Merge 241e46f9ac97998615100fe05bfbea104d600b6e into b52183867829c8e58ccfb3e3485cb4b55ec1bd20"
3: B6 Body message is missing
Bluetooth: advmon offload MSFT add monitor
1: T1 Title exceeds max length (92>72): "Merge 241e46f9ac97998615100fe05bfbea104d600b6e into b52183867829c8e58ccfb3e3485cb4b55ec1bd20"
3: B6 Body message is missing
Bluetooth: advmon offload MSFT remove monitor
1: T1 Title exceeds max length (92>72): "Merge 241e46f9ac97998615100fe05bfbea104d600b6e into b52183867829c8e58ccfb3e3485cb4b55ec1bd20"
3: B6 Body message is missing
Bluetooth: advmon offload MSFT handle controller reset
1: T1 Title exceeds max length (92>72): "Merge 241e46f9ac97998615100fe05bfbea104d600b6e into b52183867829c8e58ccfb3e3485cb4b55ec1bd20"
3: B6 Body message is missing
Bluetooth: advmon offload MSFT handle filter enablement
1: T1 Title exceeds max length (92>72): "Merge 241e46f9ac97998615100fe05bfbea104d600b6e into b52183867829c8e58ccfb3e3485cb4b55ec1bd20"
3: B6 Body message is missing
##############################
Test: CheckBuildK - PASS
##############################
Test: CheckTestRunner: Setup - PASS
##############################
Test: CheckTestRunner: l2cap-tester - PASS
Total: 40, Passed: 34 (85.0%), Failed: 0, Not Run: 6
##############################
Test: CheckTestRunner: bnep-tester - PASS
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: mgmt-tester - FAIL
Total: 416, Passed: 394 (94.7%), Failed: 8, Not Run: 14
##############################
Test: CheckTestRunner: rfcomm-tester - PASS
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: sco-tester - PASS
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: smp-tester - PASS
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: CheckTestRunner: userchan-tester - PASS
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 43340 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3530 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 548236 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11650 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9885 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11796 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5427 bytes --]
next prev parent reply other threads:[~2020-12-22 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 10:26 [PATCH v5 0/5] MSFT offloading support for advertisement monitor Archie Pusaka
2020-12-22 10:26 ` [PATCH v5 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-22 11:20 ` bluez.test.bot [this message]
2020-12-22 10:26 ` [PATCH v5 2/5] Bluetooth: advmon offload MSFT add monitor Archie Pusaka
2020-12-22 10:26 ` [PATCH v5 3/5] Bluetooth: advmon offload MSFT remove monitor Archie Pusaka
2020-12-22 10:26 ` [PATCH v5 4/5] Bluetooth: advmon offload MSFT handle controller reset Archie Pusaka
2020-12-22 10:26 ` [PATCH v5 5/5] Bluetooth: advmon offload MSFT handle filter enablement Archie Pusaka
2021-01-12 9:33 ` [PATCH v5 0/5] MSFT offloading support for advertisement monitor Archie Pusaka
-- strict thread matches above, loose matches on Subject: below --
2020-12-22 9:57 [PATCH v4 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-22 11:19 ` MSFT offloading support for advertisement monitor bluez.test.bot
2020-12-16 4:33 [PATCH v3 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-16 5:14 ` MSFT offloading support for advertisement monitor bluez.test.bot
2020-12-15 8:31 [PATCH v2 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-15 9:16 ` MSFT offloading support for advertisement monitor bluez.test.bot
2020-12-03 10:29 [PATCH v1 1/5] Bluetooth: advmon offload MSFT add rssi support Archie Pusaka
2020-12-03 11:06 ` MSFT offloading support for advertisement monitor bluez.test.bot
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=5fe1d681.1c69fb81.ff497.227e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=apusaka@google.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).