From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] adapter: wait for kernel exp features in adapter initialization
Date: Mon, 21 Aug 2023 20:00:25 +0000 [thread overview]
Message-ID: <169264802519.24934.10400065436370754752.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <00052eaeb78774fd7be365805203cb0c8b189243.1692531437.git.pav@iki.fi>
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
prev parent reply other threads:[~2023-08-21 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 11:47 [PATCH BlueZ v2] adapter: wait for kernel exp features in adapter initialization Pauli Virtanen
2023-08-20 13:23 ` [BlueZ,v2] " bluez.test.bot
2023-08-21 20:00 ` patchwork-bot+bluetooth [this message]
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=169264802519.24934.10400065436370754752.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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.