Re: [PATCH BlueZ v2 1/2] audio: actually try to enable MTU auto-tuning

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello:

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

On Wed, 29 Jan 2025 11:49:49 +0300 you wrote:
> A "0" for the input MTU passed to the underlying socket is supposed to
> indicate that its value should be determined by the L2CAP layer.
> However, the current code treats a zero imtu just as if there is
> nothing to change.
> 
> Introduce an additional flag to indicate that the zero imtu is
> explicitly requested by the caller for the purpose of auto-tuning.
> Otherwise, the similar behavior remains.
> 
> [...]

Here is the summary with links:
  - [BlueZ,v2,1/2] audio: actually try to enable MTU auto-tuning
    (no matching commit)
  - [BlueZ,v2,2/2] a2dp: enable input MTU auto-tuning for the server
    https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=252a32ac0b3f

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






[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux