Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH BlueZ] device: wait GATT client ready before service accept()
 if no cache
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <167718661757.25712.16626081241891993566.git-patchwork-notify@kernel.org>
Date:   Thu, 23 Feb 2023 21:10:17 +0000
References: <6387d20af8252ea1198c81afe728a9f67cd6bf77.1677179059.git.pav@iki.fi>
In-Reply-To: <6387d20af8252ea1198c81afe728a9f67cd6bf77.1677179059.git.pav@iki.fi>
To:     Pauli Virtanen <pav@iki.fi>
Cc:     linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

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

On Thu, 23 Feb 2023 19:14:44 +0000 you wrote:
> On device ATT attach, do not immediately call accept() for profiles, if
> there is no cached data in GATT database. Instead, wait for service
> resolution to complete, as likely accept() cannot succeed before that.
> 
> Several profiles (bap, vcp, midi, deviceinfo) assume that GATT
> attributes are available when their accept() is called, returning
> success even if not.  In this case, the services never find the remote
> attributes and are not operable.  Other profiles (hog, batt, ...) fail
> their accept which prompts core to retry after discovery, and work
> correctly also in this case.
> 
> [...]

Here is the summary with links:
  - [BlueZ] device: wait GATT client ready before service accept() if no cache
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=46a5d2beccb2

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