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 v2] adapter: wait for kernel exp features in adapter
 initialization
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <169264802519.24934.10400065436370754752.git-patchwork-notify@kernel.org>
Date:   Mon, 21 Aug 2023 20:00:25 +0000
References: <00052eaeb78774fd7be365805203cb0c8b189243.1692531437.git.pav@iki.fi>
In-Reply-To: <00052eaeb78774fd7be365805203cb0c8b189243.1692531437.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 Sun, 20 Aug 2023 14:47:06 +0300 you wrote:
> Things like BAP depend on ISO sockets being enabled in kernel.  It is
> possible the MGMT commands enabling experimental kernel features do not
> complete, before BAP etc. initialization and probing starts, in which
> case BAP will be mostly nonfunctional.
> 
> This was observed to occur always when running BlueZ in a Fedora VM,
> requiring bluetoothd restart after every boot for BAP to work,
> log containing lines in the order:
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2] adapter: wait for kernel exp features in adapter initialization
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=e93094977f08

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