From: patchwork-bot+bluetooth@kernel.org
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/3] Bluetooth: add TX timestamping for ISO and L2CAP
Date: Mon, 01 Apr 2024 20:00:38 +0000 [thread overview]
Message-ID: <171200163850.25745.15315439474290057773.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1709409547.git.pav@iki.fi>
Hello:
This series was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:
On Sat, 2 Mar 2024 22:07:35 +0200 you wrote:
> Add support for TX timestamping in ISO/L2CAP sockets.
>
> These patches allow fixing / working around controller(?) issue where
> two ISO streams in same group get desynchronized. Having accurate
> knowledge of the packet queue lengths, user application can drop packets
> if it detects the ISO streams are not in sync.
>
> [...]
Here is the summary with links:
- [1/3] Bluetooth: add support for skb TX timestamping
(no matching commit)
- [2/3] Bluetooth: ISO: add TX timestamping
https://git.kernel.org/bluetooth/bluetooth-next/c/3067d73e114f
- [3/3] Bluetooth: L2CAP: add TX timestamping
https://git.kernel.org/bluetooth/bluetooth-next/c/e22f35ed23a7
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:[~2024-04-01 20:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-02 20:07 [PATCH 0/3] Bluetooth: add TX timestamping for ISO and L2CAP Pauli Virtanen
2024-03-02 20:07 ` [PATCH 1/3] Bluetooth: add support for skb TX timestamping Pauli Virtanen
2024-03-02 20:33 ` Bluetooth: add TX timestamping for ISO and L2CAP bluez.test.bot
2024-03-04 14:36 ` [PATCH 1/3] Bluetooth: add support for skb TX timestamping Luiz Augusto von Dentz
2024-03-04 23:38 ` Pauli Virtanen
2024-03-02 20:07 ` [PATCH 2/3] Bluetooth: ISO: add " Pauli Virtanen
2024-03-02 20:07 ` [PATCH 3/3] Bluetooth: L2CAP: " Pauli Virtanen
2024-04-01 20: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=171200163850.25745.15315439474290057773.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.