Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-541-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ v1] bap: Don't attempt to release if old state was
 releasing
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <170232902367.13252.3467344920515041557.git-patchwork-notify@kernel.org>
Date: Mon, 11 Dec 2023 21:10:23 +0000
References: <20231208221219.54529-1-luiz.dentz@gmail.com>
In-Reply-To: <20231208221219.54529-1-luiz.dentz@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org

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