From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, qwertyuiopyyy@gmail.com
Subject: RE: [v2] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks
Date: Wed, 30 Sep 2026 16:06:55 -0700 (PDT) [thread overview]
Message-ID: <6abd960f.197a801a.307fc9.d61d@mx.google.com> (raw)
In-Reply-To: <20260930192249.757-1-qwertyuiopyyy@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2903 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/1177199/
---Test result---
Test Summary:
CheckPatch FAIL 0.39 seconds
VerifyFixes PASS 0.07 seconds
VerifySignedoff PASS 0.07 seconds
GitLint FAIL 0.17 seconds
SubjectPrefix PASS 0.07 seconds
BuildKernel PASS 16.64 seconds
CheckAllWarning PASS 19.65 seconds
CheckSparse PASS 30.25 seconds
BuildKernel32 PASS 16.96 seconds
CheckKernelLLVM PASS 18.18 seconds
TestRunnerSetup PASS 411.75 seconds
IncrementalBuild PASS 17.38 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#110:
Similar issue but with different device id. After patching bluetooth is working fine,
ERROR: code indent should use tabs where possible
#131: FILE: drivers/bluetooth/btusb_main.c:275:
+ { USB_DEVICE(0x0b05, 0x1825), .driver_info = BTUSB_QCA_ROME |$
WARNING: please, no spaces at the start of a line
#131: FILE: drivers/bluetooth/btusb_main.c:275:
+ { USB_DEVICE(0x0b05, 0x1825), .driver_info = BTUSB_QCA_ROME |$
ERROR: code indent should use tabs where possible
#132: FILE: drivers/bluetooth/btusb_main.c:276:
+ BTUSB_WIDEBAND_SPEECH },$
WARNING: please, no spaces at the start of a line
#132: FILE: drivers/bluetooth/btusb_main.c:276:
+ BTUSB_WIDEBAND_SPEECH },$
total: 2 errors, 3 warnings, 8 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
/home/runner/work/bluetooth-next/bluetooth-next/src/patch/14859393.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:
[v2] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks
15: B1 Line exceeds max length (85>80): "Similar issue but with different device id. After patching bluetooth is working fine,"
https://github.com/bluez/bluetooth-next/pull/846
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-09-30 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 19:22 [PATCH v2] Bluetooth: btusb: add ASUS 0b05:1825 to QCA Rome quirks Konstantin Nazarov
2026-09-30 23:06 ` 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=6abd960f.197a801a.307fc9.d61d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=qwertyuiopyyy@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