From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, ravindra@intel.com
Subject: RE: [v3] Bluetooth: btintel: read ROM debug registers on FW download failure
Date: Mon, 21 Sep 2026 04:42:41 -0700 (PDT) [thread overview]
Message-ID: <6ab11831.98a076dd.29d9d3.b8d0@mx.google.com> (raw)
In-Reply-To: <20260921054830.2770046-1-ravindra@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2152 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/1170015/
---Test result---
Test Summary:
CheckPatch FAIL 1.09 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.08 seconds
GitLint FAIL 0.24 seconds
SubjectPrefix PASS 0.08 seconds
BuildKernel PASS 29.91 seconds
CheckAllWarning PASS 34.05 seconds
CheckSparse PASS 37.61 seconds
BuildKernel32 PASS 30.12 seconds
CheckKernelLLVM PASS 34.46 seconds
TestRunnerSetup PASS 793.74 seconds
IncrementalBuild PASS 28.08 seconds
Details
##############################
Test: CheckPatch - FAIL
Desc: Run checkpatch.pl script
Output:
[v3] Bluetooth: btintel: read ROM debug registers on FW download failure
WARNING: Prefer a maximum 75 chars per line (possible unwrapped commit description?)
#94:
Bluetooth: Intel get rom debug info: dr0:0x80000001 dr1:0x00000000 dr2:0x00000001 dr3:0x00df0071
total: 0 errors, 1 warnings, 94 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/14833867.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:
[v3] Bluetooth: btintel: read ROM debug registers on FW download failure
17: B1 Line exceeds max length (98>80): " Bluetooth: Intel get rom debug info: dr0:0x80000001 dr1:0x00000000 dr2:0x00000001 dr3:0x00df0071"
https://github.com/bluez/bluetooth-next/pull/806
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-21 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 5:48 [PATCH v3] Bluetooth: btintel: read ROM debug registers on FW download failure Ravindra
2026-09-21 11:42 ` bluez.test.bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-18 8:44 Ravindra
2026-09-18 10:08 ` [v3] " bluez.test.bot
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=6ab11831.98a076dd.29d9d3.b8d0@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.