From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jlee@suse.com
Subject: RE: [1/2] Bluetooth: hci_event: Ignore NULL link key
Date: Sun, 01 Oct 2023 01:44:15 -0700 (PDT) [thread overview]
Message-ID: <6519315f.020a0220.7420d.8ca0@mx.google.com> (raw)
In-Reply-To: <20231001080813.GA14514@linux-691t>
[-- Attachment #1: Type: text/plain, Size: 2099 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=789096
---Test result---
Test Summary:
CheckPatch PASS 0.77 seconds
GitLint PASS 0.32 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 43.13 seconds
CheckAllWarning PASS 46.91 seconds
CheckSparse WARNING 53.60 seconds
CheckSmatch WARNING 140.37 seconds
BuildKernel32 PASS 41.66 seconds
TestRunnerSetup PASS 622.54 seconds
TestRunner_l2cap-tester PASS 38.78 seconds
TestRunner_iso-tester PASS 82.16 seconds
TestRunner_bnep-tester PASS 13.74 seconds
TestRunner_mgmt-tester FAIL 251.73 seconds
TestRunner_rfcomm-tester PASS 21.30 seconds
TestRunner_sco-tester PASS 24.23 seconds
TestRunner_ioctl-tester PASS 23.16 seconds
TestRunner_mesh-tester PASS 16.89 seconds
TestRunner_smp-tester PASS 20.09 seconds
TestRunner_userchan-tester PASS 15.21 seconds
IncrementalBuild PASS 40.23 seconds
Details
##############################
Test: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: CheckSmatch - WARNING
Desc: Run smatch tool with source
Output:
net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
##############################
Test: TestRunner_mgmt-tester - FAIL
Desc: Run mgmt-tester with test-runner
Output:
Total: 497, Passed: 496 (99.8%), Failed: 1, Not Run: 0
Failed Test Cases
LL Privacy - Unpair 1 Timed out 2.016 seconds
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-01 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 7:45 [PATCH 0/2] Bluetooth: ignore NULL link key and reject connection Lee, Chun-Yi
2023-10-01 7:48 ` [PATCH 1/2] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-10-01 8:14 ` Bluetooth: ignore NULL link key and reject connection bluez.test.bot
2023-10-01 8:39 ` joeyli
2023-10-01 7:48 ` [PATCH 2/2] Bluetooth: Reject connection with the device which has same BD_ADDR Lee, Chun-Yi
2023-10-01 8:05 ` [PATCH 0/2] Bluetooth: ignore NULL link key and reject connection joeyli
2023-10-01 8:08 ` [PATCH 1/2] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-10-01 8:44 ` bluez.test.bot [this message]
2023-10-01 8:09 ` [PATCH 2/2] Bluetooth: Reject connection with the device which has same BD_ADDR Lee, Chun-Yi
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=6519315f.020a0220.7420d.8ca0@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=jlee@suse.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 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.