From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, kiran.k@intel.com
Subject: RE: [v2,1/2] Bluetooth: btintel_pcie: Set only MAC_INIT in btintel_pcie_mac_init()
Date: Tue, 03 Nov 2026 09:13:35 -0800 (PST) [thread overview]
Message-ID: <6aea163f.a37de931.20a066.ab6d@mx.google.com> (raw)
In-Reply-To: <20261103143759.555315-1-kiran.k@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2907 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/1200445/
---Test result---
Test Summary:
CheckPatch FAIL 1.55 seconds
VerifyFixes PASS 0.13 seconds
VerifySignedoff PASS 0.63 seconds
GitLint FAIL 0.70 seconds
SubjectPrefix PASS 0.29 seconds
BuildKernel PASS 31.54 seconds
CheckAllWarning PASS 35.53 seconds
CheckSparse PASS 38.19 seconds
BuildKernel32 PASS 31.29 seconds
CheckKernelLLVM PASS 35.78 seconds
TestRunnerSetup PASS 764.06 seconds
IncrementalBuild PASS 33.75 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v2,1/2] Bluetooth: btintel_pcie: Set only MAC_INIT in btintel_pcie_mac_init()
WARNING: Non-standard signature: Assisted-by:
#109:
Assisted-by: Copilot:Gemini 4 Argon
ERROR: Unrecognized email address: 'Copilot:Gemini 4 Argon'
#109:
Assisted-by: Copilot:Gemini 4 Argon
total: 1 errors, 1 warnings, 18 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/14940452.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.
[v2,2/2] Bluetooth: btintel_pcie: Fold MAC_INIT into btintel_pcie_get_mac_access()
WARNING: Non-standard signature: Assisted-by:
#111:
Assisted-by: Copilot:Gemini 4 Argon
ERROR: Unrecognized email address: 'Copilot:Gemini 4 Argon'
#111:
Assisted-by: Copilot:Gemini 4 Argon
total: 1 errors, 1 warnings, 58 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/14940453.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,2/2] Bluetooth: btintel_pcie: Fold MAC_INIT into btintel_pcie_get_mac_access()
1: T1 Title exceeds max length (82>80): "[v2,2/2] Bluetooth: btintel_pcie: Fold MAC_INIT into btintel_pcie_get_mac_access()"
https://github.com/bluez/bluetooth-next/pull/1054
---
Regards,
Linux Bluetooth
prev parent reply other threads:[~2026-11-03 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 14:37 [PATCH v2 1/2] Bluetooth: btintel_pcie: Set only MAC_INIT in btintel_pcie_mac_init() Kiran K
2026-11-03 14:37 ` [PATCH v2 2/2] Bluetooth: btintel_pcie: Fold MAC_INIT into btintel_pcie_get_mac_access() Kiran K
2026-11-03 17:13 ` 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=6aea163f.a37de931.20a066.ab6d@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=kiran.k@intel.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