From: bluez.test.bot@gmail.com
To: linux-bluetooth@vger.kernel.org, frederic.danis@collabora.com
Subject: RE: input: avoid NSP1 disconnects caused by Sniff/Exit Sniff churn
Date: Wed, 26 Aug 2026 12:13:29 -0700 (PDT) [thread overview]
Message-ID: <6a8f3ad9.ee10049a.dc161.6857@mx.google.com> (raw)
In-Reply-To: <20260826164106.293951-2-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 990 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/project/bluetooth/list/?series=1152198
---Test result---
Test Summary:
CheckPatch PASS 0.63 seconds
GitLint PASS 0.40 seconds
BuildEll PASS 20.36 seconds
BluezMake PASS 597.60 seconds
MakeCheck PASS 19.56 seconds
MakeDistcheck PASS 159.04 seconds
CheckValgrind PASS 229.06 seconds
CheckSmatch PASS 312.41 seconds
bluezmakeextell PASS 103.17 seconds
IncrementalBuild PASS 601.76 seconds
ScanBuild PASS 1014.94 seconds
https://github.com/bluez/bluez/pull/2438
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-08-26 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 16:41 [PATCH BlueZ 0/2] input: avoid NSP1 disconnects caused by Sniff/Exit Sniff churn Frédéric Danis
2026-08-26 16:41 ` [PATCH BlueZ 1/2] btio: add BT_IO_OPT_FORCE_ACTIVE support for L2CAP sockets Frédéric Danis
2026-08-26 19:13 ` bluez.test.bot [this message]
2026-08-26 16:41 ` [PATCH BlueZ 2/2] profiles/input: disable force-active for Nintendo Switch Pro v1 Frédéric Danis
2026-08-26 16:58 ` [PATCH BlueZ 0/2] input: avoid NSP1 disconnects caused by Sniff/Exit Sniff churn Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2026-09-03 11:48 [PATCH BlueZ v2 1/2] btio: add BT_IO_OPT_FORCE_ACTIVE support for L2CAP sockets Frédéric Danis
2026-09-03 15:48 ` input: avoid NSP1 disconnects caused by Sniff/Exit Sniff churn 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=6a8f3ad9.ee10049a.dc161.6857@mx.google.com \
--to=bluez.test.bot@gmail.com \
--cc=frederic.danis@collabora.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