From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, me@michaelmcallister.org
Subject: RE: Bluetooth: hci_mrvl: Fix duplicate serdev open/close
Date: Sat, 14 Nov 2026 12:46:08 -0800 (PST) [thread overview]
Message-ID: <6af8c890.f21bdd07.2a9d59.a613@mx.google.com> (raw)
In-Reply-To: <179467295519.97469.5747232754111917783.marvell-serdev-v1-1@michaelmcallister.org>
[-- Attachment #1: Type: text/plain, Size: 2077 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/1211439/
---Test result---
Test Summary:
CheckPatch FAIL 0.66 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.13 seconds
GitLint PASS 0.32 seconds
SubjectPrefix PASS 0.13 seconds
BuildKernel PASS 23.28 seconds
CheckAllWarning PASS 26.65 seconds
CheckSparse WARNING 28.66 seconds
BuildKernel32 PASS 23.36 seconds
CheckKernelLLVM PASS 24.29 seconds
TestRunnerSetup PASS 550.59 seconds
IncrementalBuild PASS 22.06 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[1/1] Bluetooth: hci_mrvl: Leave the serdev port lifetime to hci_serdev
WARNING: Non-standard signature: Assisted-by:
#94:
Assisted-by: LLM
ERROR: Unrecognized email address: 'LLM'
#94:
Assisted-by: LLM
total: 1 errors, 1 warnings, 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.
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14984056.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: CheckSparse - WARNING
Desc: Run sparse tool with linux kernel
Output:
drivers/bluetooth/hci_mrvl.c:156:23: warning: restricted __le16 degrades to integerdrivers/bluetooth/hci_mrvl.c:189:23: warning: restricted __le16 degrades to integer
https://github.com/bluez/bluetooth-next/pull/1134
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-14 20:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 22:34 [PATCH 0/4] Bluetooth: qca: Fix WCN3950 power-off Michael McAllister
2026-10-28 22:34 ` [PATCH 2/4] Bluetooth: hci_serdev: Track whether the serial port is open Michael McAllister
2026-10-29 2:09 ` Bluetooth: qca: Fix WCN3950 power-off bluez.test.bot
2026-11-12 18:56 ` [PATCH 2/4] Bluetooth: hci_serdev: Track whether the serial port is open Markus Probst
2026-11-14 16:15 ` [PATCH 0/1] Bluetooth: hci_mrvl: Fix duplicate serdev open/close Michael McAllister
2026-11-14 16:15 ` [PATCH 1/1] Bluetooth: hci_mrvl: Leave the serdev port lifetime to hci_serdev Michael McAllister
2026-11-14 20:46 ` bluez.test.bot [this message]
2026-11-14 17:06 ` [PATCH 0/1] Bluetooth: hci_mrvl: Fix duplicate serdev open/close Markus Probst
2026-10-28 22:34 ` [PATCH 1/4] Bluetooth: qca: Restore flow control after a failed power pulse Michael McAllister
2026-10-28 22:34 ` [PATCH 3/4] Bluetooth: qca: Power off after unregistering the HCI device Michael McAllister
2026-10-28 22:34 ` [PATCH 4/4] Bluetooth: qca: Power off WCN3950 Michael McAllister
2026-11-14 18:39 ` [PATCH v2 0/4] " Michael McAllister
2026-11-14 18:39 ` [PATCH v2 4/4] " Michael McAllister
2026-11-14 18:39 ` [PATCH v2 1/4] Bluetooth: hci_serdev: Track whether the serial port is open Michael McAllister
2026-11-14 20:46 ` [v2,1/4] " bluez.test.bot
2026-11-14 18:39 ` [PATCH v2 2/4] Bluetooth: qca: Power off after unregistering the HCI device Michael McAllister
2026-11-14 18:39 ` [PATCH v2 3/4] Bluetooth: qca: Handle failed power-pulse writes Michael McAllister
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=6af8c890.f21bdd07.2a9d59.a613@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=me@michaelmcallister.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