From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, praneethb2002@gmail.com
Subject: RE: Bluetooth: hci_core: Hold hdev->lock when freeing an adv monitor
Date: Tue, 10 Nov 2026 16:14:13 -0800 (PST) [thread overview]
Message-ID: <6af3b355.0d30fa7d.2dfa9b.3ef6@mx.google.com> (raw)
In-Reply-To: <20261110222144.204736-1-praneeth@ucsb.edu>
[-- Attachment #1: Type: text/plain, Size: 2712 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/series/1207695/
---Test result---
Test Summary:
CheckPatch FAIL 0.78 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint FAIL 0.35 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 31.24 seconds
CheckAllWarning PASS 35.23 seconds
CheckSparse PASS 37.42 seconds
BuildKernel32 PASS 31.14 seconds
CheckKernelLLVM PASS 33.13 seconds
TestRunnerSetup PASS 745.20 seconds
TestRunner_l2cap-tester PASS 12.77 seconds
TestRunner_iso-tester PASS 10.84 seconds
TestRunner_bnep-tester PASS 3.22 seconds
TestRunner_mgmt-tester PASS 88.50 seconds
TestRunner_rfcomm-tester PASS 4.57 seconds
TestRunner_sco-tester PASS 5.75 seconds
TestRunner_ioctl-tester PASS 4.78 seconds
TestRunner_mesh-tester PASS 5.62 seconds
TestRunner_smp-tester PASS 4.44 seconds
TestRunner_userchan-tester PASS 3.29 seconds
TestRunner_6lowpan-tester PASS 4.54 seconds
IncrementalBuild PASS 29.55 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
Bluetooth: hci_core: Hold hdev->lock when freeing an adv monitor
WARNING: From:/Signed-off-by: email address mismatch: 'From: Praneeth Balasubramanian <praneethb2002@gmail.com>' != 'Signed-off-by: Praneeth Balasubramanian <praneeth@ucsb.edu>'
total: 0 errors, 1 warnings, 0 checks, 10 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14970524.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_core: Hold hdev->lock when freeing an adv monitor
34: B2 Line has trailing whitespace: " "
37: B2 Line has trailing whitespace: " "
40: B2 Line has trailing whitespace: " "
https://github.com/bluez/bluetooth-next/pull/1107
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-11 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 22:21 [PATCH] Bluetooth: hci_core: Hold hdev->lock when freeing an adv monitor Praneeth Balasubramanian
2026-11-11 0: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=6af3b355.0d30fa7d.2dfa9b.3ef6@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=praneethb2002@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox