From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ravindra@intel.com
Subject: RE: Bluetooth: btintel_pcie: fix D-state transitions and PM flows
Date: Mon, 28 Sep 2026 14:29:52 -0700 (PDT) [thread overview]
Message-ID: <6abadc50.7406aef7.f2df2.5d62@mx.google.com> (raw)
In-Reply-To: <20260928171003.2925480-2-ravindra@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2524 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/1175428/
---Test result---
Test Summary:
CheckPatch FAIL 4.04 seconds
VerifyFixes PASS 0.11 seconds
VerifySignedoff PASS 0.11 seconds
GitLint FAIL 1.09 seconds
SubjectPrefix PASS 0.43 seconds
BuildKernel PASS 20.10 seconds
CheckAllWarning PASS 24.77 seconds
CheckSparse PASS 25.41 seconds
BuildKernel32 PASS 20.70 seconds
CheckKernelLLVM PASS 20.40 seconds
TestRunnerSetup PASS 494.06 seconds
IncrementalBuild PASS 23.04 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v6,1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#94:
Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 0
total: 0 errors, 1 warnings, 22 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/14852808.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:
[v6,1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check
9: B1 Line exceeds max length (82>80): " Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 0"
10: B1 Line exceeds max length (82>80): " Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 1"
11: B1 Line exceeds max length (82>80): " Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 2"
12: B1 Line exceeds max length (98>80): " btintel_pcie 0000:00:14.7: PM: pci_pm_suspend(): btintel_pcie_suspend [btintel_pcie] returns -16"
https://github.com/bluez/bluetooth-next/pull/834
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-28 21:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 17:09 [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows Ravindra
2026-09-28 17:10 ` [PATCH v6 1/4] Bluetooth: btintel_pcie: fix stale cache in set_dxstate fallback check Ravindra
2026-09-28 21:29 ` bluez.test.bot [this message]
2026-09-28 17:10 ` [PATCH v6 2/4] Bluetooth: btintel_pcie: fix PM flow for S0ix, S3 and S4 Ravindra
2026-09-28 17:10 ` [PATCH v6 3/4] Bluetooth: btintel_pcie: verify and serialize D-state transitions Ravindra
2026-09-28 17:10 ` [PATCH v6 4/4] Bluetooth: btintel_pcie: clear the GP0 cause with a W1C write Ravindra
2026-09-28 21:14 ` [PATCH v6 0/4] Bluetooth: btintel_pcie: fix D-state transitions and PM flows Sergey Lebedev
2026-09-29 15:10 ` patchwork-bot+bluetooth
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=6abadc50.7406aef7.f2df2.5d62@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ravindra@intel.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