From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, joeyli.kernel@gmail.com
Subject: RE: Bluetooth: hci_event: Ignore NULL link key
Date: Fri, 14 Jul 2023 10:07:17 -0700 (PDT) [thread overview]
Message-ID: <64b180c5.020a0220.4fc47.4687@mx.google.com> (raw)
In-Reply-To: <20230714161210.20969-1-jlee@suse.com>
[-- Attachment #1: Type: text/plain, Size: 3181 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=765780
---Test result---
Test Summary:
CheckPatch FAIL 0.94 seconds
GitLint FAIL 0.54 seconds
SubjectPrefix PASS 0.09 seconds
BuildKernel PASS 33.91 seconds
CheckAllWarning PASS 36.79 seconds
CheckSparse WARNING 41.59 seconds
CheckSmatch WARNING 113.49 seconds
BuildKernel32 PASS 32.55 seconds
TestRunnerSetup PASS 496.37 seconds
TestRunner_l2cap-tester PASS 23.35 seconds
TestRunner_iso-tester PASS 41.73 seconds
TestRunner_bnep-tester PASS 10.61 seconds
TestRunner_mgmt-tester PASS 217.91 seconds
TestRunner_rfcomm-tester PASS 16.03 seconds
TestRunner_sco-tester PASS 16.84 seconds
TestRunner_ioctl-tester PASS 17.97 seconds
TestRunner_mesh-tester PASS 13.39 seconds
TestRunner_smp-tester PASS 14.57 seconds
TestRunner_userchan-tester PASS 11.50 seconds
IncrementalBuild PASS 31.19 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: hci_event: Ignore NULL link key
WARNING: From:/Signed-off-by: email address mismatch: 'From: "Lee, Chun-Yi" <joeyli.kernel@gmail.com>' != 'Signed-off-by: "Lee, Chun-Yi" <jlee@suse.com>'
total: 0 errors, 1 warnings, 0 checks, 12 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/13313835.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: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: hci_event: Ignore NULL link key
WARNING: I3 - ignore-body-lines: gitlint will be switching from using Python regex 'match' (match beginning) to 'search' (match anywhere) semantics. Please review your ignore-body-lines.regex option accordingly. To remove this warning, set general.regex-style-search=True. More details: https://jorisroovers.github.io/gitlint/configuration/#regex-style-search
23: B1 Line exceeds max length (81>80): "Closes: https://ieeexplore.ieee.org/abstract/document/9474325/authors#authors [2]"
##############################
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):
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2023-07-14 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 16:12 [PATCH] Bluetooth: hci_event: Ignore NULL link key Lee, Chun-Yi
2023-07-14 17:07 ` bluez.test.bot [this message]
2023-07-14 18:44 ` Luiz Augusto von Dentz
2023-07-17 5:38 ` joeyli
[not found] ` <8eeb958e-d947-2f6d-5942-d30746cf1268@web.de>
2023-07-17 5:51 ` [PATCH] Bluetooth: hci_event: Ignore NULL link key in hci_link_key_notify_evt() joeyli
[not found] ` <7cae670e-b7c5-470b-536b-ab03513cd0a3@web.de>
2023-07-17 10:23 ` joeyli
2023-07-17 11:25 ` Dan Carpenter
2023-07-17 15:48 ` joeyli
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=64b180c5.020a0220.4fc47.4687@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=joeyli.kernel@gmail.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.