From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, aluvala.sai.teja@intel.com
Subject: RE: Bluetooth: btintel_pcie: debug INI rework and fatal error injection
Date: Tue, 03 Nov 2026 00:45:27 -0800 (PST) [thread overview]
Message-ID: <6ae99f27.f51f0d36.2e39f7.5642@mx.google.com> (raw)
In-Reply-To: <20261103062832.3083624-2-aluvala.sai.teja@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1020 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/1199839/
---Test result---
Test Summary:
CheckPatch PASS 2.59 seconds
VerifyFixes PASS 0.08 seconds
VerifySignedoff PASS 0.09 seconds
GitLint PASS 1.32 seconds
SubjectPrefix PASS 0.17 seconds
BuildKernel PASS 23.27 seconds
CheckAllWarning PASS 26.47 seconds
CheckSparse PASS 28.95 seconds
BuildKernel32 PASS 23.41 seconds
CheckKernelLLVM PASS 25.62 seconds
TestRunnerSetup PASS 550.26 seconds
IncrementalBuild PASS 26.66 seconds
https://github.com/bluez/bluetooth-next/pull/1049
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-11-03 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 6:28 [PATCH v4 0/2] Bluetooth: btintel_pcie: debug INI rework and fatal error injection Sai Teja Aluvala
2026-11-03 6:28 ` [PATCH v4 1/2] Bluetooth: btintel_pcie: Move debug INI parsing to debug file Sai Teja Aluvala
2026-11-03 8:45 ` bluez.test.bot [this message]
2026-11-03 6:28 ` [PATCH v4 2/2] Bluetooth: btintel_pcie: Add fatal error injection test mode Sai Teja Aluvala
-- strict thread matches above, loose matches on Subject: below --
2026-11-02 17:37 [PATCH v3 1/2] Bluetooth: btintel_pcie: Move debug INI parsing to debug file Sai Teja Aluvala
2026-11-02 19:25 ` Bluetooth: btintel_pcie: debug INI rework and fatal error injection 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=6ae99f27.f51f0d36.2e39f7.5642@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=aluvala.sai.teja@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