From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v1] bap: Don't attempt to release if old state was releasing
Date: Mon, 11 Dec 2023 21:10:23 +0000 [thread overview]
Message-ID: <170232902367.13252.3467344920515041557.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231208221219.54529-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 8 Dec 2023 17:12:13 -0500 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> If the old state was releasing there is no reason to call
> bt_bap_stream_release yet again when IO could not be created as that
> will likely create a loop situation when the remote stack caches the
> codec configuration.
>
> [...]
Here is the summary with links:
- [BlueZ,v1] bap: Don't attempt to release if old state was releasing
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=093d00b47ee4
- [BlueZ,v2,2/6] shared/bap: Make bt_bap_select match the channel map
(no matching commit)
- [BlueZ,v2,3/6] org.bluez.MediaEndpoint: Add ChannelAllocation to SelectProperties
(no matching commit)
- [BlueZ,v2,4/6] shared/bap: Make bt_bap_select select a location
(no matching commit)
- [BlueZ,v2,5/6] shared/bap: Fix stream IO linking
(no matching commit)
- [BlueZ,v2,6/6] client/player: Use ChannelAllocation given on SelectProperties
(no matching commit)
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-12-11 21:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 22:12 [PATCH BlueZ v1] bap: Don't attempt to release if old state was releasing Luiz Augusto von Dentz
2023-12-08 22:12 ` [PATCH BlueZ v2 1/6] bap: Allow setup of multiple stream per endpoint Luiz Augusto von Dentz
2023-12-08 22:36 ` [BlueZ,v2,1/6] " bluez.test.bot
2023-12-11 22:28 ` bluez.test.bot
2023-12-08 22:12 ` [PATCH BlueZ v2 2/6] shared/bap: Make bt_bap_select match the channel map Luiz Augusto von Dentz
2023-12-08 22:12 ` [PATCH BlueZ v2 3/6] org.bluez.MediaEndpoint: Add ChannelAllocation to SelectProperties Luiz Augusto von Dentz
2023-12-08 22:12 ` [PATCH BlueZ v2 4/6] shared/bap: Make bt_bap_select select a location Luiz Augusto von Dentz
2023-12-08 22:12 ` [PATCH BlueZ v2 5/6] shared/bap: Fix stream IO linking Luiz Augusto von Dentz
2023-12-08 22:12 ` [PATCH BlueZ v2 6/6] client/player: Use ChannelAllocation given on SelectProperties Luiz Augusto von Dentz
2023-12-09 0:20 ` [BlueZ,v1] bap: Don't attempt to release if old state was releasing bluez.test.bot
2023-12-11 21:10 ` patchwork-bot+bluetooth [this message]
2023-12-15 20:50 ` [PATCH BlueZ v1] " patchwork-bot+bluetooth
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=170232902367.13252.3467344920515041557.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.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.