From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, tooangel@tooangel.de
Subject: RE: Bluetooth: MGMT: Return RFKILLED for Set Powered on a blocked controller
Date: Wed, 21 Oct 2026 05:57:12 -0700 (PDT) [thread overview]
Message-ID: <6ad8b6a8.c3449938.213f4d.5293@mx.google.com> (raw)
In-Reply-To: <20261021065833.120347-1-tooangel@tooangel.de>
[-- Attachment #1: Type: text/plain, Size: 1374 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/1190246/
---Test result---
Test Summary:
CheckPatch PASS 0.63 seconds
VerifyFixes PASS 0.26 seconds
VerifySignedoff PASS 0.14 seconds
GitLint FAIL 0.27 seconds
SubjectPrefix PASS 0.10 seconds
BuildKernel PASS 18.15 seconds
CheckAllWarning PASS 20.75 seconds
CheckSparse PASS 23.78 seconds
BuildKernel32 PASS 19.03 seconds
CheckKernelLLVM PASS 20.97 seconds
TestRunnerSetup PASS 404.56 seconds
TestRunner_mgmt-tester PASS 80.42 seconds
TestRunner_mesh-tester PASS 4.98 seconds
IncrementalBuild PASS 17.38 seconds
Details
##############################
Test: GitLint - FAIL
Desc: Run gitlint
Output:
Bluetooth: MGMT: Return RFKILLED for Set Powered on a blocked controller
35: B2 Line has trailing whitespace: " "
37: B2 Line has trailing whitespace: " "
https://github.com/bluez/bluetooth-next/pull/970
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-10-21 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 6:58 [PATCH] Bluetooth: MGMT: Return RFKILLED for Set Powered on a blocked controller Tobias Wilken
2026-10-21 12:57 ` bluez.test.bot [this message]
2026-10-23 22: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=6ad8b6a8.c3449938.213f4d.5293@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=tooangel@tooangel.de \
/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