From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, 2045gemini@gmail.com
Subject: RE: Bluetooth: Fix atomicity violation in {min,max}_key_size_set
Date: Fri, 22 Dec 2023 03:31:49 -0800 (PST) [thread overview]
Message-ID: <658573a5.050a0220.458fa.703e@mx.google.com> (raw)
In-Reply-To: <20231222105813.9245-1-2045gemini@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4143 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=812453
---Test result---
Test Summary:
CheckPatch FAIL 0.86 seconds
GitLint FAIL 4.55 seconds
SubjectPrefix PASS 0.29 seconds
BuildKernel PASS 28.09 seconds
CheckAllWarning PASS 30.56 seconds
CheckSparse PASS 36.39 seconds
CheckSmatch PASS 104.63 seconds
BuildKernel32 PASS 27.69 seconds
TestRunnerSetup PASS 437.81 seconds
TestRunner_l2cap-tester PASS 23.23 seconds
TestRunner_iso-tester PASS 43.32 seconds
TestRunner_bnep-tester PASS 7.37 seconds
TestRunner_mgmt-tester PASS 164.45 seconds
TestRunner_rfcomm-tester PASS 11.13 seconds
TestRunner_sco-tester PASS 14.89 seconds
TestRunner_ioctl-tester PASS 12.20 seconds
TestRunner_mesh-tester PASS 8.92 seconds
TestRunner_smp-tester PASS 10.32 seconds
TestRunner_userchan-tester PASS 7.44 seconds
IncrementalBuild PASS 26.40 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: Fix atomicity violation in {min,max}_key_size_set
WARNING: Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")' - ie: 'Fixes: ("Bluetooth: Move {min,max}_key_size debugfs ...")'
#120:
Fixes: 18f81241b74fb ("Bluetooth: Move {min,max}_key_size debugfs ...")
WARNING: Reported-by: should be immediately followed by Closes: with a URL to the report
#122:
Reported-by: BassCheck <bass@buaa.edu.cn>
Signed-off-by: Gui-Dong Han <2045gemini@gmail.com>
ERROR: trailing whitespace
#138: FILE: net/bluetooth/hci_debugfs.c:1048:
+^I$
ERROR: trailing whitespace
#155: FILE: net/bluetooth/hci_debugfs.c:1078:
+^I$
total: 2 errors, 2 warnings, 0 checks, 32 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.
NOTE: Whitespace errors detected.
You may wish to use scripts/cleanpatch or scripts/cleanfile
/github/workspace/src/src/13503200.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.
Use of uninitialized value $cid in concatenation (.) or string at /github/workspace/src/src/scripts/checkpatch.pl line 3228.
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: Fix atomicity violation in {min,max}_key_size_set
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
4: B3 Line contains hard tab characters (\t): " if (val > hdev->le_max_key_size || val < SMP_MIN_ENC_KEY_SIZE)"
5: B3 Line contains hard tab characters (\t): " return -EINVAL;"
6: B3 Line contains hard tab characters (\t): " hci_dev_lock(hdev);"
7: B3 Line contains hard tab characters (\t): " hdev->le_min_key_size = val;"
8: B3 Line contains hard tab characters (\t): " hci_dev_unlock(hdev);"
11: B3 Line contains hard tab characters (\t): " if (val > SMP_MAX_ENC_KEY_SIZE || val < hdev->le_min_key_size)"
12: B3 Line contains hard tab characters (\t): " return -EINVAL;"
13: B3 Line contains hard tab characters (\t): " hci_dev_lock(hdev);"
14: B3 Line contains hard tab characters (\t): " hdev->le_max_key_size = val;"
15: B3 Line contains hard tab characters (\t): " hci_dev_unlock(hdev);"
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2023-12-22 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-22 10:58 [PATCH] Bluetooth: Fix atomicity violation in {min,max}_key_size_set Gui-Dong Han
2023-12-22 11:31 ` 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=658573a5.050a0220.458fa.703e@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=2045gemini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).