Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ 1/2] transport: handle BAP Enabling state correctly when
 resuming
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <168858002496.7518.8837283986593270105.git-patchwork-notify@kernel.org>
Date:   Wed, 05 Jul 2023 18:00:24 +0000
References: <8af1dd5097cc4411ff2681ed39c49c232f817ebe.1688326228.git.pav@iki.fi>
In-Reply-To: <8af1dd5097cc4411ff2681ed39c49c232f817ebe.1688326228.git.pav@iki.fi>
To:     Pauli Virtanen <pav@iki.fi>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sun,  2 Jul 2023 22:34:18 +0300 you wrote:
> If BAP stream is in Enabling state when transport acquire is attempted,
> we should wait for bap_state_changed to emit the completion event.
> 
> transport->resume() is only called with new owner with no
> owner->pending, and shall return nonzero completion id on success.
> Currently if BAP stream is Enabling, it returns zero which fails the
> acquire operation.
> 
> [...]

Here is the summary with links:
  - [BlueZ,1/2] transport: handle BAP Enabling state correctly when resuming
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=466fce0209a3
  - [BlueZ,2/2] shared/bap: use only nonzero req->id
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=8fd0c76b41d3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html