[lvc-project] [PATCH] Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection
patchwork-bot+bluetooth at kernel.org
patchwork-bot+bluetooth at kernel.org
Wed Jan 29 23:20:32 MSK 2025
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz at intel.com>:
On Wed, 29 Jan 2025 00:08:14 +0300 you wrote:
> One of the possible ways to enable the input MTU auto-selection for L2CAP
> connections is supposed to be through passing a special "0" value for it
> as a socket option. Commit [1] added one of those into avdtp. However, it
> simply wouldn't work because the kernel still treats the specified value
> as invalid and denies the setting attempt. Recorded BlueZ logs include the
> following:
>
> [...]
Here is the summary with links:
- Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection
https://git.kernel.org/bluetooth/bluetooth-next/c/257a2b95631f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
More information about the lvc-project
mailing list