From: patchwork-bot+bluetooth@kernel.org
To: =?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] device: Reply br-connection-key-missing on connection bonding error
Date: Thu, 15 May 2025 20:10:29 +0000 [thread overview]
Message-ID: <174733982976.3234907.15623202795049448255.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250515163448.189497-1-frederic.danis@collabora.com>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Thu, 15 May 2025 18:34:48 +0200 you wrote:
> Currently when connection is removed while the client is waiting for
> Connect() the failed message is br-connection-canceled, even if this
> is due to bonding error.
>
> Implement to reply with br-connection-key-missing, when the connection
> request fails due to a bonding authentication error, allowing the client
> to differentiate connection failure reasons.
>
> [...]
Here is the summary with links:
- [BlueZ,v2] device: Reply br-connection-key-missing on connection bonding error
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=00969bdb17ea
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-05-15 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 16:34 [PATCH BlueZ v2] device: Reply br-connection-key-missing on connection bonding error Frédéric Danis
2025-05-15 18:02 ` [BlueZ,v2] " bluez.test.bot
2025-05-15 20:10 ` 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=174733982976.3234907.15623202795049448255.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc==?utf-8?b?RnLDqWTDqXJpYyBEYW5pcyA8ZnJlZGVyaWMuZGFuaXNAY29sbGFib3JhLmNvbT4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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.