From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v3 1/6] btdev: Add support for Sync Flow Control
Date: Tue, 11 Mar 2025 15:50:34 +0000 [thread overview]
Message-ID: <174170823425.132061.7780763071835633975.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <747adb1a5f2a6b7b25e823bf22f8795f4c7c6322.1741370367.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluez.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Fri, 7 Mar 2025 20:00:54 +0200 you wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> This adds support for Sync Flow Control by supporting command
> Write Sync Flow Control Enable:
>
> < HCI Command: Write Sync Fl.. (0x03|0x002f) plen 1
> Flow control: Enabled (0x01)
> > HCI Event: Command Complete (0x0e) plen 4
> Write Sync Flow Control Enable (0x03|0x002f) ncmd 1
> Status: Success (0x00)
>
> [...]
Here is the summary with links:
- [BlueZ,v3,1/6] btdev: Add support for Sync Flow Control
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=86d6b74ff002
- [BlueZ,v3,2/6] btdev: send SCO setup events to bthost
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=b7ef134eb978
- [BlueZ,v3,3/6] bthost: add hooks receiving SCO connections and data
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=ce1abc32b3fc
- [BlueZ,v3,4/6] sco-tester: check sent SCO data is received at bthost
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=87d4f95dc312
- [BlueZ,v3,5/6] btdev: support disabling commands
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=7da93164f483
- [BlueZ,v3,6/6] sco-tester: add tests for different SCO flow control modes
https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=95055def8cd2
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-11 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-07 18:00 [PATCH BlueZ v3 1/6] btdev: Add support for Sync Flow Control Pauli Virtanen
2025-03-07 18:00 ` [PATCH BlueZ v3 2/6] btdev: send SCO setup events to bthost Pauli Virtanen
2025-03-07 18:00 ` [PATCH BlueZ v3 3/6] bthost: add hooks receiving SCO connections and data Pauli Virtanen
2025-03-07 18:00 ` [PATCH BlueZ v3 4/6] sco-tester: check sent SCO data is received at bthost Pauli Virtanen
2025-03-07 18:00 ` [PATCH BlueZ v3 5/6] btdev: support disabling commands Pauli Virtanen
2025-03-07 18:00 ` [PATCH BlueZ v3 6/6] sco-tester: add tests for different SCO flow control modes Pauli Virtanen
2025-03-07 19:17 ` [BlueZ,v3,1/6] btdev: Add support for Sync Flow Control bluez.test.bot
2025-03-11 15:50 ` 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=174170823425.132061.7780763071835633975.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.