From: patchwork-bot+bluetooth@kernel.org
To: Ludovico de Nittis <ludovico.denittis@collabora.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Bluetooth: hci_event: Fix connection state issues during suspend/resume
Date: Tue, 19 Aug 2025 14:30:06 +0000 [thread overview]
Message-ID: <175561380625.3572360.2079025948323464029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250812155527.995119-1-ludovico.denittis@collabora.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 12 Aug 2025 17:55:25 +0200 you wrote:
> This patch series addresses connection state synchronization issues
> between the Bluetooth controller and kernel during suspend/resume cycles.
>
> The problem seems to be visible when using devices that very quickly try
> to send multiple reconnect events without waiting enough for the host
> to fully resume from suspend.
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: hci_event: Treat UNKNOWN_CONN_ID on disconnect as success
https://git.kernel.org/bluetooth/bluetooth-next/c/f6305e06185a
- [v2,2/2] Bluetooth: hci_event: Mark connection as closed during suspend disconnect
https://git.kernel.org/bluetooth/bluetooth-next/c/e090ee03a6ed
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-19 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 15:55 [PATCH v2 0/2] Bluetooth: hci_event: Fix connection state issues during suspend/resume Ludovico de Nittis
2025-08-12 15:55 ` [PATCH v2 1/2] Bluetooth: hci_event: Treat UNKNOWN_CONN_ID on disconnect as success Ludovico de Nittis
2025-08-12 16:40 ` Bluetooth: hci_event: Fix connection state issues during suspend/resume bluez.test.bot
2025-08-12 15:55 ` [PATCH v2 2/2] Bluetooth: hci_event: Mark connection as closed during suspend disconnect Ludovico de Nittis
2025-08-19 14:30 ` patchwork-bot+bluetooth [this message]
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=175561380625.3572360.2079025948323464029.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ludovico.denittis@collabora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox