From: patchwork-bot+bluetooth@kernel.org
To: Kevin Dewald <kevin@simpleble.org>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com
Subject: Re: [PATCH BlueZ] bearer: Fix Connect refused as in progress after a failed attempt
Date: Tue, 10 Nov 2026 16:40:07 +0000 [thread overview]
Message-ID: <179432880792.4080412.17915800166430164235.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261110080311.71913-1-kevin@simpleble.org>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Tue, 10 Nov 2026 00:03:11 -0800 you wrote:
> Connect keeps the method call in bearer->connect before starting the
> connection, and releases it when the connection completes or fails.
> When the connection cannot even be started, as when the adapter is
> powered off, the call is answered with an error right away but stays
> in bearer->connect. Every later Connect on that bearer is then refused
> with org.bluez.Error.InProgress, until the device connects some other
> way.
>
> [...]
Here is the summary with links:
- [BlueZ] bearer: Fix Connect refused as in progress after a failed attempt
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=89a7a7cad54b
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:[~2026-11-10 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 8:03 [PATCH BlueZ] bearer: Fix Connect refused as in progress after a failed attempt Kevin Dewald
2026-11-10 12:14 ` [BlueZ] " bluez.test.bot
2026-11-10 16:40 ` 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=179432880792.4080412.17915800166430164235.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=kevin@simpleble.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 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.