From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, jlee@suse.com
Subject: RE: Bluetooth: ignore NULL link key and reject connection with the device which has same BD_ADDR
Date: Sun, 01 Oct 2023 01:39:50 -0700 (PDT) [thread overview]
Message-ID: <65193056.0c0a0220.8bb55.174a@mx.google.com> (raw)
In-Reply-To: <20231001081046.GA14551@linux-691t>
[-- Attachment #1: Type: text/plain, Size: 3111 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=789095
---Test result---
Test Summary:
CheckPatch FAIL 1.88 seconds
GitLint PASS 0.71 seconds
SubjectPrefix PASS 0.25 seconds
BuildKernel PASS 36.22 seconds
CheckAllWarning PASS 38.57 seconds
CheckSparse WARNING 44.78 seconds
CheckSmatch WARNING 117.53 seconds
BuildKernel32 PASS 34.05 seconds
TestRunnerSetup PASS 513.44 seconds
TestRunner_l2cap-tester PASS 31.39 seconds
TestRunner_iso-tester PASS 61.14 seconds
TestRunner_bnep-tester PASS 10.66 seconds
TestRunner_mgmt-tester PASS 229.05 seconds
TestRunner_rfcomm-tester PASS 16.26 seconds
TestRunner_sco-tester PASS 19.68 seconds
TestRunner_ioctl-tester PASS 18.55 seconds
TestRunner_mesh-tester PASS 13.47 seconds
TestRunner_smp-tester PASS 14.49 seconds
TestRunner_userchan-tester PASS 11.19 seconds
IncrementalBuild PASS 39.54 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[2/2] Bluetooth: Reject connection with the device which has same BD_ADDR
ERROR: that open brace { should be on the previous line
#144: FILE: net/bluetooth/hci_conn.c:1615:
+ if (!bacmp(&hdev->bdaddr, dst))
+ {
ERROR: that open brace { should be on the previous line
#162: FILE: net/bluetooth/hci_event.c:3272:
+ if (!bacmp(&hdev->bdaddr, &ev->bdaddr))
+ {
WARNING: line length of 108 exceeds 100 columns
#164: FILE: net/bluetooth/hci_event.c:3274:
+ bt_dev_dbg(hdev, "Reject connection from the device with same BD_ADDR %pMR\n", &ev->bdaddr);
total: 2 errors, 1 warnings, 0 checks, 27 lines checked
NOTE: For some of the reported defects, checkpatch may be able to
mechanically convert to the typical style using --fix or --fix-inplace.
/github/workspace/src/src/13405302.patch has style problems, please review.
NOTE: Ignored message types: UNKNOWN_COMMIT_ID
NOTE: If any of the errors are false positives, please report
them to the maintainer, see CHECKPATCH in MAINTAINERS.
##############################
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):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):net/bluetooth/hci_event.c: note: in included file (through include/net/bluetooth/hci_core.h):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-10-01 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-01 8:03 [PATCH 0/2] Bluetooth: ignore NULL link key and reject connection with the device which has same BD_ADDR Lee, Chun-Yi
2023-10-01 8:10 ` [PATCH 1/2] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-10-01 8:39 ` bluez.test.bot [this message]
2023-10-01 8:11 ` [PATCH 2/2] Bluetooth: Reject connection with the device which has same BD_ADDR Lee, Chun-Yi
-- strict thread matches above, loose matches on Subject: below --
2023-10-01 8:59 [PATCH 1/2] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-10-01 9:37 ` Bluetooth: ignore NULL link key and reject connection with the device which has same BD_ADDR 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=65193056.0c0a0220.8bb55.174a@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.