From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, arnd@kernel.org
Subject: RE: Bluetooth: hci_event: shut up a false-positive warning
Date: Wed, 22 Nov 2023 14:56:44 -0800 (PST) [thread overview]
Message-ID: <655e872c.620a0220.f2a0c.00a7@mx.google.com> (raw)
In-Reply-To: <20231122221805.3139482-1-arnd@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2506 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=803455
---Test result---
Test Summary:
CheckPatch PASS 0.49 seconds
GitLint FAIL 0.55 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 27.95 seconds
CheckAllWarning PASS 30.80 seconds
CheckSparse WARNING 36.13 seconds
CheckSmatch WARNING 99.31 seconds
BuildKernel32 PASS 27.12 seconds
TestRunnerSetup PASS 418.45 seconds
TestRunner_l2cap-tester PASS 22.80 seconds
TestRunner_iso-tester PASS 44.52 seconds
TestRunner_bnep-tester PASS 7.03 seconds
TestRunner_mgmt-tester PASS 162.09 seconds
TestRunner_rfcomm-tester PASS 10.98 seconds
TestRunner_sco-tester PASS 14.46 seconds
TestRunner_ioctl-tester PASS 12.36 seconds
TestRunner_mesh-tester PASS 9.12 seconds
TestRunner_smp-tester PASS 9.84 seconds
TestRunner_userchan-tester PASS 7.45 seconds
IncrementalBuild PASS 25.87 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: hci_event: shut up a false-positive warning
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
9: B1 Line exceeds max length (143>80): "net/bluetooth/hci_event.c:524:9: error: 'memcpy' writing 3 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]"
##############################
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-11-22 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 22:17 [PATCH] Bluetooth: hci_event: shut up a false-positive warning Arnd Bergmann
2023-11-22 22:56 ` bluez.test.bot [this message]
2023-11-25 7:01 ` Dan Carpenter
2023-11-25 6:58 ` [PATCH] " kernel test robot
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=655e872c.620a0220.f2a0c.00a7@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=arnd@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox