From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, yury.norov@gmail.com
Subject: RE: net/bluetooth: fix erroneous use of bitmap_from_u64()
Date: Sun, 05 Jun 2022 10:14:46 -0700 (PDT) [thread overview]
Message-ID: <629ce486.1c69fb81.a7fb5.3c68@mx.google.com> (raw)
In-Reply-To: <20220605162537.1604762-1-yury.norov@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2839 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=647461
---Test result---
Test Summary:
CheckPatch FAIL 1.95 seconds
GitLint FAIL 1.03 seconds
SubjectPrefix FAIL 0.87 seconds
BuildKernel PASS 36.71 seconds
BuildKernel32 PASS 32.83 seconds
Incremental Build with patchesPASS 44.05 seconds
TestRunner: Setup PASS 546.12 seconds
TestRunner: l2cap-tester PASS 18.98 seconds
TestRunner: bnep-tester PASS 6.98 seconds
TestRunner: mgmt-tester PASS 113.33 seconds
TestRunner: rfcomm-tester PASS 10.88 seconds
TestRunner: sco-tester PASS 10.46 seconds
TestRunner: smp-tester PASS 10.53 seconds
TestRunner: userchan-tester PASS 7.30 seconds
Details
##############################
Test: CheckPatch - FAIL - 1.95 seconds
Run checkpatch.pl script with rule in .checkpatch.conf
net/bluetooth: fix erroneous use of bitmap_from_u64()\WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line)
#117:
inlined from 'bitmap_copy_clear_tail' at ./include/linux/bitmap.h:263:2,
total: 0 errors, 1 warnings, 0 checks, 33 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/12869809.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 - 1.03 seconds
Run gitlint with rule in .gitlint
net/bluetooth: fix erroneous use of bitmap_from_u64()
26: B1 Line exceeds max length (85>80): " inlined from 'hci_bdaddr_list_add_with_flags' at net/bluetooth/hci_core.c:2156:2:"
27: B1 Line exceeds max length (113>80): "./include/linux/fortify-string.h:344:25: error: call to '__write_overflow_field' declared with attribute warning:"
28: B1 Line exceeds max length (107>80): "+detected write beyond size of field (1st parameter); maybe use struct_group()? [-Werror=attribute-warning]"
43: B1 Line exceeds max length (115>80): "./include/linux/bitmap.h:254:9: error: 'memcpy' forming offset [4, 7] is out of the bounds [0, 4] of object 'flags'"
##############################
Test: SubjectPrefix - FAIL - 0.87 seconds
Check subject contains "Bluetooth" prefix
"Bluetooth: " is not specified in the subject
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2022-06-05 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 16:25 [PATCH] net/bluetooth: fix erroneous use of bitmap_from_u64() Yury Norov
2022-06-05 16:34 ` Linus Torvalds
2022-06-05 18:51 ` Linus Torvalds
2022-06-05 23:56 ` Linus Torvalds
2022-06-07 6:00 ` Luiz Augusto von Dentz
2022-06-07 18:49 ` Linus Torvalds
2022-06-05 17:14 ` 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=629ce486.1c69fb81.a7fb5.3c68@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=yury.norov@gmail.com \
/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.