From: patchwork-bot+bluetooth@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: linux-bluetooth@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH BlueZ v2 1/2] audio: actually try to enable MTU auto-tuning
Date: Thu, 30 Jan 2025 17:30:34 +0000 [thread overview]
Message-ID: <173825823449.1027237.5797702882442522177.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250129084950.41987-1-pchelkin@ispras.ru>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
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
next prev parent reply other threads:[~2025-01-30 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-29 8:49 [PATCH BlueZ v2 1/2] audio: actually try to enable MTU auto-tuning Fedor Pchelkin
2025-01-29 8:49 ` [PATCH BlueZ v2 2/2] a2dp: enable input MTU auto-tuning for the server Fedor Pchelkin
2025-01-29 10:09 ` [BlueZ,v2,1/2] audio: actually try to enable MTU auto-tuning bluez.test.bot
2025-01-30 17:30 ` patchwork-bot+bluetooth [this message]
2025-01-30 17:51 ` [PATCH BlueZ v2 1/2] " Luiz Augusto von Dentz
2025-01-31 11:16 ` Fedor Pchelkin
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=173825823449.1027237.5797702882442522177.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=pchelkin@ispras.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox