From: patchwork-bot+bluetooth@kernel.org
To: Simon Mikuda <simon.mikuda@streamunlimited.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/2] Report proper error on connect
Date: Mon, 07 Aug 2023 23:20:22 +0000 [thread overview]
Message-ID: <169145042259.20955.11298055921488554509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230806080109.1639693-1-simon.mikuda@streamunlimited.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sun, 6 Aug 2023 10:01:07 +0200 you wrote:
> When we connect A2DP profile and remote device doesn't have our key
> (e.g. was deleted) we've received "unknown" error.
>
> These patches add mapping to "Invalid exchange" error which is returned
> in this use case as "key missing" error.
>
> Simon Mikuda (2):
> error: Add "Invalid exchange" mapping
> a2dp: Expose "Key missing" error
>
> [...]
Here is the summary with links:
- [BlueZ,1/2] error: Add "Invalid exchange" mapping
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=0ee60b31a843
- [BlueZ,2/2] a2dp: Expose "Key missing" error
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=59569c1f947d
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:[~2023-08-07 23:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 8:01 [PATCH BlueZ 0/2] Report proper error on connect Simon Mikuda
2023-08-06 8:01 ` [PATCH BlueZ 1/2] error: Add "Invalid exchange" mapping Simon Mikuda
2023-08-06 9:51 ` Report proper error on connect bluez.test.bot
2023-08-06 8:01 ` [PATCH BlueZ 2/2] a2dp: Expose "Key missing" error Simon Mikuda
2023-08-07 23:20 ` 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=169145042259.20955.11298055921488554509.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=simon.mikuda@streamunlimited.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