From: patchwork-bot+bluetooth@kernel.org
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO
Date: Thu, 13 Mar 2025 14:00:32 +0000 [thread overview]
Message-ID: <174187443201.1524310.8087699036754748717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250312151421.201772-1-luiz.dentz@gmail.com>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Wed, 12 Mar 2025 11:14:20 -0400 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This enables buffer flow control for SCO/eSCO
> (see: Bluetooth Core 6.0 spec: 6.22. Synchronous Flow Control Enable),
> recently this has caused the following problem and is actually a nice
> addition for the likes of Socket TX complete:
>
> [...]
Here is the summary with links:
- [v2,1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO
https://git.kernel.org/bluetooth/bluetooth-next/c/174f3c12f664
- [v2,2/2] Bluetooth: hci_vhci: Mark Sync Flow Control as supported
https://git.kernel.org/bluetooth/bluetooth-next/c/5c301fb00b84
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:[~2025-03-13 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 15:14 [PATCH v2 1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO Luiz Augusto von Dentz
2025-03-12 15:14 ` [PATCH v2 2/2] Bluetooth: hci_vhci: Mark Sync Flow Control as supported Luiz Augusto von Dentz
2025-03-12 15:37 ` [v2,1/2] Bluetooth: hci_core: Enable buffer flow control for SCO/eSCO bluez.test.bot
2025-03-12 20:00 ` [PATCH v2 1/2] " Pauli Virtanen
2025-03-12 20:30 ` Luiz Augusto von Dentz
2025-03-13 14: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=174187443201.1524310.8087699036754748717.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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.