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: Fri, 18 Sep 2026 10:39:41 -0700 (PDT) [thread overview]
Message-ID: <6aad775d.f7f62383.8f14d.ce19@mx.google.com> (raw)
In-Reply-To: <20260903114849.777525-2-frederic.danis@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
This is an automated email and please do not reply to this email.
Dear Submitter,
This series was picked up by the CI more than 2 weeks ago and the pull
request created for it is still open, which means the series was never
applied to the tree.
Series: input: avoid NSP1 disconnects caused by Sniff/Exit Sniff churn
Pull Request: https://github.com/bluez/bluez/pull/2480
Created: 2026-09-03 14:59:47+00:00
The pull request has been closed and no further action is taken on this
series.
If the change should still be considered, it must be resent to the Linux
Bluetooth mailing list (linux-bluetooth@vger.kernel.org) so that it is
picked up again.
---
Regards,
Linux Bluetooth
next prev parent reply other threads:[~2026-09-18 17:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 11:48 [PATCH BlueZ v2 0/2] input: avoid NSP1 disconnects caused by Sniff/Exit Sniff churn Frédéric Danis
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
2026-09-18 17:39 ` bluez.test.bot [this message]
2026-09-03 11:48 ` [PATCH BlueZ v2 2/2] profiles/input: disable force-active for Nintendo Switch Pro v1 Frédéric Danis
-- strict thread matches above, loose matches on Subject: below --
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 ` 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=6aad775d.f7f62383.8f14d.ce19@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 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.