From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, linma@zju.edu.cn
Subject: RE: [v0] bluetooth: fix data races in smp_unregister(), smp_del_chan()
Date: Tue, 15 Feb 2022 20:00:03 -0800 (PST) [thread overview]
Message-ID: <620c76c3.1c69fb81.fa102.5e3a@mx.google.com> (raw)
In-Reply-To: <20220216033619.10821-1-linma@zju.edu.cn>
[-- Attachment #1: Type: text/plain, Size: 1961 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=614788
---Test result---
Test Summary:
CheckPatch PASS 1.61 seconds
GitLint FAIL 1.06 seconds
SubjectPrefix FAIL 0.86 seconds
BuildKernel PASS 30.92 seconds
BuildKernel32 PASS 27.23 seconds
Incremental Build with patchesPASS 37.01 seconds
TestRunner: Setup PASS 475.85 seconds
TestRunner: l2cap-tester PASS 13.55 seconds
TestRunner: bnep-tester PASS 6.14 seconds
TestRunner: mgmt-tester PASS 105.79 seconds
TestRunner: rfcomm-tester FAIL 7.67 seconds
TestRunner: sco-tester PASS 7.74 seconds
TestRunner: smp-tester PASS 7.70 seconds
TestRunner: userchan-tester PASS 6.51 seconds
Details
##############################
Test: GitLint - FAIL - 1.06 seconds
Run gitlint with rule in .gitlint
[v0] bluetooth: fix data races in smp_unregister(), smp_del_chan()
37: B1 Line exceeds max length (81>80): "[ 49.097146] =================================================================="
69: B1 Line exceeds max length (85>80): "[ 49.097611] RSP: 002b:00007f5a59d6abc0 EFLAGS: 00000246 ORIG_RAX: 000000000000002c"
##############################
Test: SubjectPrefix - FAIL - 0.86 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
##############################
Test: TestRunner: rfcomm-tester - FAIL - 7.67 seconds
Run test-runner with rfcomm-tester
Total: 10, Passed: 9 (90.0%), Failed: 1, Not Run: 0
Failed Test Cases
Basic RFCOMM Socket Client - Write 32k Success Failed 0.154 seconds
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-02-16 4:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 3:36 [PATCH v0] bluetooth: fix data races in smp_unregister(), smp_del_chan() Lin Ma
2022-02-16 4:00 ` bluez.test.bot [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=620c76c3.1c69fb81.fa102.5e3a@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linma@zju.edu.cn \
--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 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.