From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] bap: handle state transitions with old_state == new_state
Date: Wed, 15 Nov 2023 00:30:23 +0000 [thread overview]
Message-ID: <170000822346.23786.1390579434951329167.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <e8a45a4796f024825318996d68d1b92ebcc9b04a.1699652713.git.pav@iki.fi>
Hello:
This patch was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 10 Nov 2023 23:48:19 +0200 you wrote:
> ASCS allows transitions from Codec/QoS Configured back to the same
> state.
>
> E.g. NRF5340_AUDIO devkit starts in the config(1) state, which is
> allowed (only Config QoS, Release, Enable, Receiver Stop Ready
> transition are client-only). In this case, as client, we do Config Codec
> ourselves and end up with config(1)->config(1) transition. We currently
> ignore that event, so QoS won't be setup and transports won't be
> created.
>
> [...]
Here is the summary with links:
- [BlueZ,v2] bap: handle state transitions with old_state == new_state
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8b035b70f379
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-11-15 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 21:48 [PATCH BlueZ v2] bap: handle state transitions with old_state == new_state Pauli Virtanen
2023-11-10 23:26 ` [BlueZ,v2] " bluez.test.bot
2023-11-15 0: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=170000822346.23786.1390579434951329167.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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