From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: RE: [1/2] Bluetooth: L2CAP: Fix invalid access if ECRED Reconfigure fails
Date: Wed, 19 May 2021 14:09:31 -0700 (PDT) [thread overview]
Message-ID: <60a57e8b.1c69fb81.9b6e3.57fa@mx.google.com> (raw)
In-Reply-To: <20210519204151.1087613-1-luiz.dentz@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2630 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=485329
---Test result---
Test Summary:
CheckPatch PASS 1.40 seconds
GitLint PASS 0.33 seconds
BuildKernel PASS 569.82 seconds
TestRunner: Setup PASS 380.04 seconds
TestRunner: l2cap-tester PASS 2.79 seconds
TestRunner: bnep-tester PASS 1.98 seconds
TestRunner: mgmt-tester PASS 27.09 seconds
TestRunner: rfcomm-tester PASS 2.17 seconds
TestRunner: sco-tester PASS 2.05 seconds
TestRunner: smp-tester PASS 2.22 seconds
TestRunner: userchan-tester PASS 2.00 seconds
Details
##############################
Test: CheckPatch - PASS - 1.40 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
##############################
Test: GitLint - PASS - 0.33 seconds
Run gitlint with rule in .gitlint
##############################
Test: BuildKernel - PASS - 569.82 seconds
Build Kernel with minimal configuration supports Bluetooth
##############################
Test: TestRunner: Setup - PASS - 380.04 seconds
Setup environment for running Test Runner
##############################
Test: TestRunner: l2cap-tester - PASS - 2.79 seconds
Run test-runner with l2cap-tester
Total: 40, Passed: 40 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: bnep-tester - PASS - 1.98 seconds
Run test-runner with bnep-tester
Total: 1, Passed: 1 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: mgmt-tester - PASS - 27.09 seconds
Run test-runner with mgmt-tester
Total: 416, Passed: 403 (96.9%), Failed: 0, Not Run: 13
##############################
Test: TestRunner: rfcomm-tester - PASS - 2.17 seconds
Run test-runner with rfcomm-tester
Total: 9, Passed: 9 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: sco-tester - PASS - 2.05 seconds
Run test-runner with sco-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: smp-tester - PASS - 2.22 seconds
Run test-runner with smp-tester
Total: 8, Passed: 8 (100.0%), Failed: 0, Not Run: 0
##############################
Test: TestRunner: userchan-tester - PASS - 2.00 seconds
Run test-runner with userchan-tester
Total: 3, Passed: 3 (100.0%), Failed: 0, Not Run: 0
---
Regards,
Linux Bluetooth
[-- Attachment #2: l2cap-tester.log --]
[-- Type: application/octet-stream, Size: 44350 bytes --]
[-- Attachment #3: bnep-tester.log --]
[-- Type: application/octet-stream, Size: 3556 bytes --]
[-- Attachment #4: mgmt-tester.log --]
[-- Type: application/octet-stream, Size: 546863 bytes --]
[-- Attachment #5: rfcomm-tester.log --]
[-- Type: application/octet-stream, Size: 11677 bytes --]
[-- Attachment #6: sco-tester.log --]
[-- Type: application/octet-stream, Size: 9912 bytes --]
[-- Attachment #7: smp-tester.log --]
[-- Type: application/octet-stream, Size: 11823 bytes --]
[-- Attachment #8: userchan-tester.log --]
[-- Type: application/octet-stream, Size: 5454 bytes --]
next prev parent reply other threads:[~2021-05-19 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 20:41 [PATCH 1/2] Bluetooth: L2CAP: Fix invalid access if ECRED Reconfigure fails Luiz Augusto von Dentz
2021-05-19 20:41 ` [PATCH 2/2] Bluetooth: L2CAP: Fix invalid access on ECRED Connection response Luiz Augusto von Dentz
2021-05-20 15:19 ` Marcel Holtmann
2021-05-19 21:09 ` bluez.test.bot [this message]
2021-05-20 15:19 ` [PATCH 1/2] Bluetooth: L2CAP: Fix invalid access if ECRED Reconfigure fails Marcel Holtmann
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=60a57e8b.1c69fb81.9b6e3.57fa@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 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).